Procedure, base station and user equipment for uplink transmission without grant

ABSTRACT

A user equipment (UE) is described. The UE receives a RRC message including a periodicity. The UE also receives the RRC message including a first parameter. The UE further receives on a physical downlink control channel, DCI with CRC scrambled by a first RNTI that is different from a C-RNTI. The UE additionally performs, in a case that the first parameter is configured, a first PUSCH transmission based on the periodicity and a first offset value, the first offset value being configured by using the RRC message. The UE also performs, in a case that the first parameter is not configured, a second PUSCH transmission based on the periodicity and a second offset value, the second offset value being indicated by using the DCI, the second PUSCH transmission being activated by using the DCI.

RELATED APPLICATIONS

This application is related to and claims priority from U.S. ProvisionalPatent Application No. 62/520,518, entitled “PROCEDURE, BASE STATION ANDUSER EQUIPMENT FOR UPLINK TRANSMISSION WITHOUT GRANT,” filed on Jun. 15,2017, which is hereby incorporated by reference herein, in its entirety.

TECHNICAL FIELD

The present disclosure relates generally to communication systems. Morespecifically, the present disclosure relates to hybrid automatic repeatrequest (HARQ) for uplink ultra-reliable and low-latency communications(URLLC).

BACKGROUND

Wireless communication devices have become smaller and more powerful inorder to meet consumer needs and to improve portability and convenience.Consumers have become dependent upon wireless communication devices andhave come to expect reliable service, expanded areas of coverage andincreased functionality. A wireless communication system may providecommunication for a number of wireless communication devices, each ofwhich may be serviced by a base station. A base station may be a devicethat communicates with wireless communication devices.

As wireless communication devices have advanced, improvements incommunication capacity, speed, flexibility and/or efficiency have beensought. However, improving communication capacity, speed, flexibility,and/or efficiency may present certain problems.

For example, wireless communication devices may communicate with one ormore devices using a communication structure. However, the communicationstructure used may only offer limited flexibility and/or efficiency. Asillustrated by this discussion, systems and methods that improvecommunication flexibility and/or efficiency may be beneficial.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating one implementation of one or morebase stations (gNBs) and one or more user equipments (UEs) in whichsystems and methods for ultra-reliable and low-latency communication(URLLC) operations may be implemented;

FIG. 2 is diagram illustrating some examples of grant-based URLLC andgrant-based eMBB;

FIG. 3 is a diagram illustrating some examples of grant-based URLLC andgrant-based eMBB;

FIG. 4 is a diagram illustrating examples of grant-free URLLC andgrant-based eMBB;

FIG. 5 is a diagram illustrating examples of grant-based URLLC andgrant-free eMBB;

FIG. 6 is a diagram illustrating examples of grant-based initialtransmission and grant-free initial transmission;

FIGS. 7A-7B are diagrams illustrating examples of grant-basedretransmission and grant-free initial transmission;

FIG. 8 is a diagram illustrating examples of grant-free initialtransmission and grant-free retransmission;

FIG. 9 is a diagram illustrating examples of grant-based retransmissionand grant-free retransmission;

FIG. 10 is a diagram illustrating examples of synchronous HARQ andasynchronous HARQ;

FIGS. 11A-11B are diagrams illustrating examples of mini-slots;

FIG. 12 is a diagram illustrating examples of HARQ procedures;

FIG. 13 is a diagram illustrating examples of repetitions;

FIG. 14 is a diagram illustrating examples of grant-free transmission;

FIGS. 15A-15B are diagrams illustrating examples of multiple HARQprocesses;

FIG. 16 is a diagram illustrating an example of a resource grid for thedownlink;

FIG. 17 is a diagram illustrating one example of a resource grid for theuplink;

FIG. 18 shows examples of several numerologies;

FIG. 19 shows examples of subframe structures for the numerologies thatare shown in FIG. 18;

FIG. 20 shows examples of slots and sub-slots;

FIG. 21 shows examples of scheduling timelines;

FIG. 22 shows examples of downlink (DL) control channel monitoringregions;

FIG. 23 shows examples of DL control channel which includes more thanone control channel elements;

FIG. 24 shows examples of uplink (UL) control channel structures;

FIG. 25 is a block diagram illustrating one implementation of a gNB;

FIG. 26 is a block diagram illustrating one implementation of a UE;

FIG. 27 illustrates various components that may be utilized in a UE;

FIG. 28 illustrates various components that may be utilized in a gNB;

FIG. 29 is a block diagram illustrating one implementation of a UE inwhich systems and methods for ultra-reliable and low-latencycommunication operations may be implemented;

FIG. 30 is a block diagram illustrating one implementation of a gNB inwhich systems and methods for ultra-reliable and low-latencycommunication operations may be implemented;

FIG. 31 is a flow diagram illustrating a method of a user equipment(UE); and

FIG. 32 is a flow diagram illustrating a communication method of a basestation apparatus (gNB).

DETAILED DESCRIPTION

A user equipment (UE) is described. The UE includes receiving circuitryconfigured to receive a radio resource control (RRC) message including aperiodicity. The receiving circuitry is also configured to receive theRRC message including a first parameter. The receiving circuitry isfurther configured to receive on a physical downlink control channel,downlink control information (DCI) with cyclic redundancy check (CRC)scrambled by a first radio network temporary identifier (RNTI) that isdifferent from a cell-RNTI (C-RNTI). The UE also includes transmittingcircuitry configured to perform, in a case that the first parameter isconfigured, a first PUSCH transmission based on the periodicity and afirst offset value, the first offset value being configured by using theRRC message. The transmitting circuitry is also configured to perform,in a case that the first parameter is not configured, a second PUSCHtransmission based on the periodicity and a second offset value, thesecond offset value being indicated by using the DCI, the second PUSCHtransmission being activated by using the DCI.

A base station apparatus is also described. The base station apparatusincludes transmitting circuitry configured to transmit a radio resourcecontrol (RRC) message including a periodicity. The transmittingcircuitry is also configured to transmit the RRC message including afirst parameter. The transmitting circuitry is further configured totransmit on a physical downlink control channel, downlink controlinformation (DCI) with cyclic redundancy check (CRC) scrambled by afirst radio network temporary identifier (RNTI) that is different from acell-RNTI (C-RNTI). The base station apparatus also includes receivingcircuitry configured to receive, in a case that the first parameter isconfigured, a first PUSCH transmission based on the periodicity and afirst offset value, the first offset value being configured by using theRRC message. The receiving circuitry is also configured to receive, in acase that the first parameter is not configured, a second PUSCHtransmission based on the periodicity and a second offset value, thesecond offset value being indicated by using the DCI, the second PUSCHtransmission being activated by using the DCI.

A communication method of a user equipment is also described. The methodincludes receiving a radio resource control (RRC) message comprising aperiodicity. The method also includes receiving the RRC messagecomprising a first parameter. The method further includes receiving on aphysical downlink control channel, downlink control information (DCI)with cyclic redundancy check (CRC) scrambled by a first radio networktemporary identifier (RNTI) that is different from a cell-RNTI (C-RNTI).The method additionally includes transmitting, in a case that the firstparameter is configured, a first PUSCH transmission based on theperiodicity and a first offset value, the first offset value beingconfigured by using the RRC message. The method also includestransmitting, in a case that the first parameter is not configured, asecond PUSCH transmission based on the periodicity and a second offsetvalue, the second offset value being indicated by using the DCI, thesecond PUSCH transmission being activated by using the DCI.

A communication method of a base station apparatus is also described.The method includes transmitting a radio resource control (RRC) messagecomprising a periodicity. The method also includes transmitting the RRCmessage comprising a first parameter. The method further includestransmitting on a physical downlink control channel, downlink controlinformation (DCI) with cyclic redundancy check (CRC) scrambled by afirst radio network temporary identifier (RNTI) that is different from acell-RNTI (C-RNTI). The method additionally includes receiving, in acase that the first parameter is configured, a first PUSCH transmissionbased on the periodicity and a first offset value, the first offsetvalue being configured by using the RRC message. The method alsoincludes receiving, in a case that the first parameter is notconfigured, a second PUSCH transmission based on the periodicity and asecond offset value, the second offset value being indicated by usingthe DCI, the second PUSCH transmission being activated by using the DCI.

The 3rd Generation Partnership Project, also referred to as “3GPP,” is acollaboration agreement that aims to define globally applicabletechnical specifications and technical reports for third and fourthgeneration wireless communication systems. The 3GPP may definespecifications for next generation mobile networks, systems and devices.

3GPP Long Term Evolution (LTE) is the name given to a project to improvethe Universal Mobile Telecommunications System (UMTS) mobile phone ordevice standard to cope with future requirements. In one aspect, UMTShas been modified to provide support and specification for the EvolvedUniversal Terrestrial Radio Access (E-UTRA) and Evolved UniversalTerrestrial Radio Access Network (E-UTRAN).

At least some aspects of the systems and methods disclosed herein may bedescribed in relation to the 3GPP LTE, LTE-Advanced (LTE-A) and otherstandards (e.g., 3GPP Releases 8, 9, 10, 11 and/or 12). However, thescope of the present disclosure should not be limited in this regard. Atleast some aspects of the systems and methods disclosed herein may beutilized in other types of wireless communication systems.

A wireless communication device may be an electronic device used tocommunicate voice and/or data to a base station, which in turn maycommunicate with a network of devices (e.g., public switched telephonenetwork (PSTN), the Internet, etc.). In describing systems and methodsherein, a wireless communication device may alternatively be referred toas a mobile station, a UE, an access terminal, a subscriber station, amobile terminal, a remote station, a user terminal, a terminal, asubscriber unit, a mobile device, etc. Examples of wirelesscommunication devices include cellular phones, smart phones, personaldigital assistants (PDAs), laptop computers, netbooks, e-readers,wireless modems, etc. In 3GPP specifications, a wireless communicationdevice is typically referred to as a UE. However, as the scope of thepresent disclosure should not be limited to the 3GPP standards, theterms “UE” and “wireless communication device” may be usedinterchangeably herein to mean the more general term “wirelesscommunication device.” A UE may also be more generally referred to as aterminal device.

In 3GPP specifications, a base station is typically referred to as aNode B, an evolved Node B (eNB), a home enhanced or evolved Node B(HeNB) or some other similar terminology. As the scope of the disclosureshould not be limited to 3GPP standards, the terms “base station,” “NodeB,” “eNB,” “gNB” and/or “HeNB” may be used interchangeably herein tomean the more general term “base station.” Furthermore, the term “basestation” may be used to denote an access point. An access point may bean electronic device that provides access to a network (e.g., Local AreaNetwork (LAN), the Internet, etc.) for wireless communication devices.The term “communication device” may be used to denote both a wirelesscommunication device and/or a base station. An eNB may also be moregenerally referred to as a base station device.

It should be noted that as used herein, a “cell” may be anycommunication channel that is specified by standardization or regulatorybodies to be used for International Mobile Telecommunications-Advanced(IMT-Advanced) and all of it or a subset of it may be adopted by 3GPP aslicensed bands (e.g., frequency bands) to be used for communicationbetween an eNB and a UE. It should also be noted that in E-UTRA andE-UTRAN overall description, as used herein, a “cell” may be defined as“combination of downlink and optionally uplink resources.” The linkingbetween the carrier frequency of the downlink resources and the carrierfrequency of the uplink resources may be indicated in the systeminformation transmitted on the downlink resources.

“Configured cells” are those cells of which the UE is aware and isallowed by an eNB to transmit or receive information. “Configuredcell(s)” may be serving cell(s). The UE may receive system informationand perform the required measurements on all configured cells.“Configured cell(s)” for a radio connection may include a primary celland/or no, one, or more secondary cell(s). “Activated cells” are thoseconfigured cells on which the UE is transmitting and receiving. That is,activated cells are those cells for which the UE monitors the physicaldownlink control channel (PDCCH) and in the case of a downlinktransmission, those cells for which the UE decodes a physical downlinkshared channel (PDSCH). “Deactivated cells” are those configured cellsthat the UE is not monitoring the transmission PDCCH. It should be notedthat a “cell” may be described in terms of differing dimensions. Forexample, a “cell” may have temporal, spatial (e.g., geographical) andfrequency characteristics.

Fifth generation (5G) cellular communications (also referred to as “NewRadio,” “New Radio Access Technology” or “NR” by 3GPP) envisions the useof time/frequency/space resources to allow for enhanced mobile broadband(eMBB) communication and ultra-reliable low-latency communication(URLLC) services, as well as massive machine type communication (MMTC)like services. A new radio base station may be referred to as a gNB. AgNB may also be more generally referred to as a base station device.

Some configurations of the systems and methods described herein teachapproaches for URLLC transmission/retransmission management to meet thelatency/reliability requirement. Some requirements for URLLC relate touser (U)-plane latency and reliability. For URLLC, the target user planelatency is 0.5 milliseconds (ms) each way for both uplink (UL) anddownlink (DL). The target reliability is 1-10⁻⁵ for X bytes within 1milliseconds (ms).

These URLLC-specific constraints make the hybrid automatic repeatrequest (HARQ) and retransmission mechanism design difficult. Forexample, the receiver must reply with a quick acknowledgement (ACK) ornegative acknowledgement (NACK) or an uplink grant to meet the latencyrequirement, or the transmitter can retransmit immediately withoutwaiting for ACK/NACK to enhance the reliability. On the other,grant-based or grant-free repetitions are supported to further enhancethe reliability. How to terminate the repetitions is also an importantissue. The described systems and methods teach URLLC HARQ/retransmissiondesign in different cases.

Some configurations of the systems and methods disclosed herein mayprovide a hybrid automatic repeat request (HARQ) mechanism design foruplink ultra-reliable and low-latency communications (URLLC).

URLLC UE may support several kinds of UL transmission In someimplementations. Some potential kinds of supported UL transmissions aredescribed as follows. One kind of UL transmission may be (a) ascheduling request-triggered uplink grant-based initial transmission.For example, when the UE has data to transmit and has no PUSCH resource,the UE may send out a scheduling request (SR) and wait for an UL grantfrom the gNB/eNB. Then, the UE may transmit the UL data by following theUL grant.

Another kind of UL transmission may be (b) a fast UL grant-based initialtransmission. The gNB/eNB may send an UL grant to the UE without SRtriggering. The fast grant can help minimize the waiting time. Then, theUE may transmit the UL data by following the UL grant.

Another kind of UL transmission may be (c) a grant-free initialtransmission. The resource may be semi-statically (re-) configured forUL transmission. The UE may transmit UL data at the configured resourcewithout waiting for an UL grant.

Another kind of UL transmission may be (d) a grant-based repetition(s).For an UL transmission scheme with grant, K repetitions includinginitial transmission (K>=1) for the same transport block may besupported. The repetition number K may be semi-statically (re-)configured or dynamically indicated by the UL grant. Then, the UErepeats K UL transmissions for the same transport block (TB) byfollowing the UL grant. In other words, an UL grant can trigger multipletransmissions for the same TB.

Another kind of UL transmission may be (e) a grant-free repetition(s).For an UL transmission scheme without grant, K repetitions includinginitial transmission (K>=1) for the same transport block may besupported. The resource may be semi-statically (re-) configured for UL Krepetitions. The resource configuration may include time and frequencyresources, Modulation and Coding Scheme (MCS), Redundancy Version (RV),Reference Signal (RS) parameter, and/or repetition number K, etc. The UEmay transmit K repetitions for the same UL data at the configuredresource without waiting for an UL grant.

Another kind of UL transmission may be a (f) grant-based retransmission.If the gNB/eNB fails to decode the UL data from a UE, the gNB/eNB maysend the UE an UL grant to indicate an UL retransmission of the same TB.Additional information in the UL grant may be needed to inform the UEwhether the grant is for the same TB or a new TB. Then, the UE maytransmit the UL data by following the UL grant.

Another kind of UL transmission may be a (g) grant-free retransmission.The UE may retransmit the same TB at a configured resource withoutwaiting for the response (e.g., negative acknowledgment (NACK) or ULgrant) from the gNB/eNB.

Another kind of UL transmission may be (h) an UL semi-persistentscheduling (SPS) transmission. For semi-static resource allocation (alsoreferred to as semi-persistent scheduling, SPS), there may be severalbasic procedures: radio resource control (RRC) configuration (e.g., aRRC message, a RRC signal), activation, UL transmission anddeactivation. The RRC configuration may be exchanged between the gNB/eNBand the UE through an RRC layer. And, the RRC signal may be included ina higher layer signal. Some of the parameters (e.g., periodicity,address, allocation, and MCS to be used in the SPS resources) may needto be configured for semi-persistent scheduling. Part of theseparameters (e.g., periodicity, address) may be configuredsemi-statically (SPS Configuration), and the rest may be configured withPDCCH (SPS Activation). For example, the gNB/eNB may configure aperiodicity (e.g., a time resource) by using the RRC signal, andindicate SPS resource (e.g., a frequency resource) by using DCI formatfor activation. After UL SPS is configured and activated, the UE knowsthat configured UL grant-free resources are reserved for fast uplinkaccess. Then, the UE may start UL transmission. In Release 8, the UEkeeps transmitting at the configured resources until UL SPS isdeactivated explicitly and implicitly. In Release 14, the UE maytransmit as needed and skip the configured resources when there is notransport block (TB) for transmission.

In some implementations, the transmission types above may overlap witheach other. For example, transmission types (a), (b) and (f) mayoverlap. To a UE, these UL transmissions may be grant-based. The UEbehavior following the UL grant can be the same and the PDCCH can usethe same DCI format. If the UL grant is indicated for the same TB, theUL transmission is a retransmission. If the UL grant is indicated for anew TB, the UL transmission is an initial transmission.

In another example, transmission types (a), (b) and (d) (or (c) and (e))may overlap. If the repetition number K=1, they may be equivalent.

In yet another example, transmission types (c) ((e), (g)) and (h) mayoverlap. The grant-free transmission may use the UL SPS scheme. In aspecial design, the grant-free transmission may use the UL SPS schemewithout activation. For instance, all the required parameters for ULtransmission may be RRC (re-)configured, and the UE may transmit at theconfigured resource without SPS activation.

In yet another example, transmission types (d), (e) and (g) may overlap.The repetition(s) followed by the initial transmission may belong to agrant-free retransmission.

For URLLC, the UE may have one or more kinds of Radio Network TemporaryIdentifiers (RNTIs). The RNTI may be used to scramble the cyclicredundancy check (CRC) part of the radio channel messages. This impliesthat if the UE does not know the exact RNTI values for each of thecases, the UE cannot decode the radio channel messages. Examples ofRNTIs that may be utilized by a UE are given as follows. One example isa Cell RNTI (C-RNTI). Here, the C-RNTI herein may be assumed to beincluded in a RNTI “A” in some implementations for the sake of simpledescription. The C-RNTI may be used for dynamic scheduled unicasttransmission. Another example is a SPS C-RNTI. The SPS C-RNTI may beused for semi-persistent scheduled unicast transmission (activation,reactivation, retransmission, and/or deactivation). Here, the SPS C-RNTIherein may be assumed to be included in a RNTI “B” in someimplementations for the sake of simple description. Yet another exampleis a URLLC C-RNTI. For URLLC, the UE may reuse the C-RNTI and the SPSC-RNTI, which means no specific C-RNTI may be issued for URLLC. In adifferent design, a URLLC-specific identification called URLLC C-RNTI(the specification may use a different name, here “URLLC C-RNTI” is usedas an example) may be used for URLLC related transmission. The URLLCC-RNTI may be used for dynamic scheduled transmission. Additionally oralternatively, the URLLC C-RNTI may be used for semi-persistentscheduled URLLC transmission (activation, reactivation, retransmission,and/or deactivation). Also, the URLLC C-RNTI may be used for dynamicreconfiguration of UL grant-free URLLC transmission. Here, the URLLCC-RNTI herein may be assumed to be included in a RNTI “C” in someimplementations for the sake of simple description.

Here, the UE may monitor a set of candidates of the DL controlchannel(s) (e.g., the PDCCH). For example, the candidates of DL controlchannel(s) may be candidates for which the DL control channel(s) maypossibly be mapped, assigned, and/or transmitted. For example, acandidate of the DL control channel(s) is composed of one or morecontrol channel elements (CCEs). The term “monitor” means that the UEattempts to decode each DL control channel(s) in the set of candidatesof the DL control channel(s) in accordance with all the DCI format(s) tobe monitored.

The set of candidates of the DL control channel(s) which the UE monitorsmay be also referred to as a search space (e.g., DL control channel set,etc.). That is, the search space is a set of resource(s) that maypossibly be used for transmission of the DL control channel(s).

Here, a common search space (CSS) and a user-equipment search space(USS) are set (or defined, configured) in a region(s) of DL controlchannel(s) (e.g., the DL control channel monitoring regions). Forexample, the CSS may be used for transmission of DCI to a plurality ofthe UEs. That is, the CSS may be defined by a resource common to aplurality of the UEs. For example, the CSS is composed of CCEs havingnumbers that are predetermined between the gNB and the UE. For example,the CSS is composed of CCEs having indices 0 to 15. Also, the gNB mayconfigure (by using the PBCH (e.g., the MIB), the PDSCH (i.e., the SIB),and/or the dedicated RRC message) the CSS (e.g., the region of the CSS).

Here, the CSS may be used for transmission of DCI to a specific UE. Thatis, the gNB may transmit, in the CSS, DCI format(s) intended for aplurality of the UEs and/or DCI format(s) intended for a specific UE.

The USS may be used for transmission of DCI to a specific UE. That is,the USS is defined by a resource dedicated to a certain UE. That is, theUSS may be defined independently for each UE. For example, the USS maybe composed of CCEs having numbers that are determined based on a RadioNetwork Temporary Identifier (RNTI), a slot number in a radio frame, anaggregation level, and/or the like. The RNTI(s) may be assigned (i.e.,configured) by the gNB. Namely, each of the USSs corresponding to eachof the RNTI(s) described below may be defined. Also, for example, thegNB may configure (by using the PBCH (e.g., the MIB), the PDSCH (e.g.,the SIB), and/or the dedicated RRC message) the USS (e.g., the region ofthe USS). Also, the gNB may transmit, in the USS, DCI format(s) intendedfor a specific UE.

Here, the RNTI(s) assigned to the UE may be used for transmission of DCI(transmission of DL control channel(s)). Specifically, CRC (CyclicRedundancy Check) parity bits (also referred to simply as CRC), whichare generated based on DCI (or the DCI format, and/or the UL grant), areattached to DCI, and, after attachment, the CRC parity bits arescrambled by the RNTI(s). The UE may attempt to decode DCI to which theCRC parity bits scrambled by the RNTI(s) are attached, and detects a DLcontrol channel (e.g., the PCCH (e.g., the PDCCH), the DCI, the DCIformat). That is, the UE may decode the DL control channel(s) with theCRC scrambled by the RNTI(s). That is, the UE may monitor the DL controlchannel(s) with the RNTI(s). Namely, for example, the UE may monitor theUL grant with the RNTI(s).

Namely, some types of UL data transmissions (e.g., PUSCH transmissions),such as those described as from (a) to (h) may be instructed by the gNB.For example, the gNB may instruct some types of UL data transmission byusing the different method as above described. Namely, for example,different RNTIs may be used for identifying the instructions for thedifferent types of UL data transmissions. Also, different DCI formats(i.e., the different UL grants) may be used for identifying theinstructions for the different types of UL data transmissions. Also, thedifferent physical downlink channels may be used for identifying theinstructions for the different types of UL data transmissions. Also,different periodicities for UL data transmission may be used foridentifying the instruction for the different types of UL datatransmission. Also, different values of DCI (i.e., different values towhich a field(s) of DCI is set) included in the DCI format may be usedfor identifying the instruction for the different types of UL datatransmissions. Also, different activation methods (i.e., differentactivation commands) for UL data transmission (e.g., different RNTIs maybe used for the different activation method and/or different values ofDCI may be used for different activation command) may be used foridentifying the instructions for the different types of UL datatransmission. Also, different HARQ process IDs (i.e., a different numberof a HARQ process) may be used for identifying the instructions for thedifferent types of UL data transmission. Also, the different RRCconfiguration and/or the different DCI indication may be used foridentifying the instructions for the different types of UL datatransmission.

As one example, a first UL data transmission, a second UL datatransmission, and a third UL data transmission may be described. Here,as one example, the first UL data transmission, the second UL datatransmission, and the third UL data transmission are described herein,and other types of UL data transmissions, such as those described from(a) to (h) may not be precluded.

For example, the first UL data transmission (the initial transmissionand/or the retransmission) may be instructed by using a first UL grant.And, the first UL grant may be used for scheduling of a first PUSCH. Forexample, the UE monitors the first UL grant in the search space(s)(i.e., the UE-specific search space and/or the common search space) onthe primary cell and in the space(s) on the secondary cell. For example,the first UL grant may be the UL grant with a first RNTI. Here, thefirst RNTI may be the C-RNTI. For example, the first RNTI may beincluded in the RRC message used to request the re-establishment of anRRC connection. Also, for example, the first RNTI may be transmittedtogether with a physical cell identifier. Also, the first RNTI may beincluded in the RRC message used for network controlled mobility (e.g.,the RRC message includes parameters relevant for network controlledmobility (i.e., a mobility control)). Also, the first UL grant may bedifferent from a second UL grant, a third UL grant, and/or a fourth ULgrant. Also, the first UL grant may be the same as the second UL grant,the third UL grant, and/or the fourth UL grant. Also, the first UL grantmay include DCI indicating a starting position(s) of a time resource ofthe PUSCH and/or DCI indicating an ending positions(s) of time resourceof the PUSCH. Also, the first UL grant may include DCI indicating theHARQ process ID. Namely, the first UL grant may be used for schedulingof more than two symbols (i.e., a subframe, a slot, a sub-slot (i.e.,mini-slot), and/or a symbol) of PUSCH. For example, the first UL grantmay be used for dynamically scheduling of the PUSCH (e.g., dynamicallyPUSCH scheduling of eMBB data transmission).

Also, for example, the second UL data transmission (the initialtransmission and/or the retransmission) may be instructed by using asecond UL grant. And, the second UL grant may be used for scheduling ofa second PUSCH. For example, the UE monitors the second UL grant in thesearch space(s) (i.e., the UE-specific search space and/or the commonsearch space) only on the primary cell. For example, the second UL grantmay be the UL grant with a second RNTI. Here, the second RNTI may be theSPS C-RNTI. For example, the second RNTI may be included in the RRCmessage used to specify the semi-persistent configuration. For example,the second RNTI may be transmitted together with the interval ofsemi-persistent scheduling (e.g., the subframe and/or slot basedinterval of semi-persistent scheduling). Also, the second UL grant maybe different from the first UL grant, the third UL grant, and/or thefourth UL grant. Also, the second UL grant may be the same as the firstUL grant, the third UL grant, and/or the fourth UL grant. Here, thesecond UL grant may be used for activating and/or deactivating (e.g.,releasing) of SPS (SPS resource). Also, the second UL grant may includeDCI indicating the HARQ process ID. For example, the second UL datatransmission may be scheduled by using the RRC configuration (e.g., theconfiguration of the interval (e.g., the subframe and/or the slot basedinterval of the semi-persistent scheduling)) and the second UL grant(i.e., the activation command). Namely, the second UL grant may be usedfor scheduling of more than two symbols (i.e., a subframe, a slot, asub-slot (i.e., mini-slot), and/or a symbol) of PUSCH. Namely, thesecond UL grant may be used for semi-persistently scheduling of thePUSCH (e.g., semi-persistently PUSCH scheduling of SPS data transmission(e.g., UL-SCH transmission)).

Also, for example, the third UL data transmission (the initialtransmission, the retransmission, and/or the repetition) may beinstructed by using a third UL grant. And, the third UL grant may beused for scheduling of a third PUSCH. For example, the UE monitors thethird UL grant in the search space(s) (i.e., the UE-specific searchspace and/or the common search space) on the primary cell and in thespace(s) on the secondary cell. Here, the third UL grant may be the ULgrant with a third RNTI. For example, the third RNTI may be the URLLCC-RNTI. Also, the third RNTI may be the C-RNTI. Also, the third RNTI maybe the SPS C-RNTI. Namely, the third RNTI may be included in the RRCmessage used to request the re-establishment of an RRC connection. Also,the third RNTI may be transmitted together with a physical cellidentifier. Also, the third RNTI may be included in the RRC message usedfor network controlled mobility. Also, the third RNTI may be included inthe RRC message used to specify the semi-persistent configuration. Forexample, the third RNTI may be transmitted together with the interval ofsemi-persistent scheduling (e.g., the slot, the sub-slot (i.e., themini-slot) and/or the symbol based interval of semi-persistentscheduling). Also, the third UL grant may be different from a first ULgrant, a second UL grant, and/or a fourth UL grant. Also, the third ULgrant may be the same as the first UL grant, the second UL grant, and/orthe fourth UL grant. For example, in a case that the C-RNTI and/or theSPS C-RNTI is used for the third RNTI, each of one or more firstpredetermined fields included in the third UL grant may be set to eachof first predetermined values for identifying the third UL grant. Here,the each of one or more first predetermined fields and/or the each ofone or more first predetermined values may be defined, in advance, bythe specification, and known information between the gNB and the UE.Namely, the third UL grant may be used for scheduling of equal to orless than two symbols (i.e., a sub-slot (i.e., mini-slot) and/or asymbol) of PUSCH. Also, the third UL grant may include DCI indicatingthe HARQ process ID. For example, the third UL grant may be used fordynamic grant-based scheduling of the PUSCH (e.g., grant-based PUSCHscheduling of URLLC data transmission).

Also, for example, the fourth UL data transmission (the initialtransmission, the retransmission, and/or the repetition) may beinstructed by using a fourth UL grant. And, the fourth UL grant may beused for scheduling of a fourth PUSCH. For example, the UE monitors thefourth UL grant in the search space(s) (i.e., the UE-specific searchspace and/or the common search space) on the primary cell and in thespace(s) on the secondary cell. Here, the fourth UL grant may be the ULgrant with a fourth RNTI. For example, the fourth RNTI may be the SPSC-RNTI. Also, the fourth RNTI may be the C-RNTI. Also, the fourth RNTImay be the URLLC C-RNTI. Namely, the fourth RNTI may be included in theRRC message used to request the re-establishment of an RRC connection.Also, the fourth RNTI may be transmitted together with a physical cellidentifier. Also, the fourth RNTI may be included in the RRC messageused for network controlled mobility. Also, the fourth RNTI may beincluded in the RRC message used to specify the semi-persistentconfiguration. For example, the fourth RNTI may be transmitted togetherwith the interval of semi-persistent scheduling (e.g., the slot and/orsymbol based interval of semi-persistent scheduling). Also, the fourthUL grant may be different from the first UL grant, the second UL grant,and/or the third UL grant. Also, the fourth UL grant may be the same asthe first UL grant, the second UL grant, and/or the third UL grant.Here, the fourth UL grant may be used for activating and/or deactivating(e.g., releasing) of SPS (SPS resource). For example, the fourth UL datatransmission may be scheduled by using the RRC configuration (e.g., theconfiguration of the interval (e.g., subframe, slot, and/or slot basedinterval of the semi-persistent scheduling, and/or URLLC semi-persistentscheduling) and the fourth UL grant (i.e., the activation command). Forexample, in a case that the C-RNTI and/or the SPS C-RNTI is used for thefourth RNTI, each of one or more second predetermined fields included inthe fourth UL grant may be set to each of second predetermined valuesfor identifying the fourth UL grant. Here, the each of one or moresecond predetermined fields and/or the each of one or more secondpredetermined values may be defined, in advance, by the specification,and known information between the gNB and the UE. Namely, the fourth ULgrant may be used for scheduling of equal to or less than two symbols(i.e., a sub-slot (i.e., mini-slot), and/or a symbol) of the PUSCH.Also, the fourth UL grant may include DCI indicating the HARQ processID. For example, the fourth UL grant may be used for semi-persistentgrant-free scheduling of the PUSCH (e.g., grant-free PUSCH scheduling ofURLLC data transmission).

And, as described above, the first UL data transmission, the second ULdata transmission, the third UL data transmission, and/or the fourth ULdata transmission may be overlapped in a certain timing (e.g., in asubframe, in a slot, in a sub-slot (i.e., a mini-slot), and/or in asymbol). Namely, the first UL data transmission, the second UL datatransmission, the third UL data transmission, and/or the fourth UL datatransmission may occur in a certain same timing. And, in a case that thefirst UL data transmission, the second UL data transmission, the thirdUL data transmission, and/or the fourth UL data transmission would occurin the certain same timing, the second UL data transmission, the thirdUL data transmission, and/or the fourth UL data transmission may beprioritized. Here, as described above, a time length of the first ULdata transmission, the second UL data transmission, the third UL datatransmission, and/or the fourth UL data transmission may be different.Therefore, the meaning of the overlapped may be a partially overlappedin the certain same timing.

For example, in a case that the first UL data transmission and thesecond UL data transmission would occur in the certain timing (i.e., inthe certain same timing), the UE may perform only the first UL datatransmission using the first PUSCH in the certain timing. Namely, thesecond UL data transmission may be dropped. Also, in a case that thefirst UL data transmission and the second UL data transmission wouldoccur in the certain same timing, the UE may perform only the second ULdata transmission using the second PUSCH in the certain timing. Namely,the first UL data transmission may be dropped. Also, in a case that thefirst UL data transmission and the second UL data transmission wouldoccur in the certain same timing, the UE may perform the first UL datatransmission and the second UL data transmission using the first PUSCHin the certain timing. Also, in a case that the first UL datatransmission and the second UL data transmission would occur in thecertain same timing, the UE may perform the first UL data transmissionand the second UL data transmission using the second PUSCH in thecertain timing. Here, the gNB may transmit, (e.g., by using the RRCmessage), information used for configuring (i.e., indicating) thatwhether a simultaneous transmission (i.e., a concurrent transmission) ofthe first UL data (i.e., the first PUSCH transmission) and the second ULdata (i.e., the second PUSCH transmission) is allowed or not in thecertain timing. Namely, in a case that the UE is configured with thesimultaneous transmission of the first UL data and the second UL data,the UE may perform the first UL data transmission and the second UL datatransmission in the certain timing. Also, the gNB may transmit (e.g., byusing the RRC message) information used for configuring which UL datatransmission is performed (e.g., which UL data transmission isprioritized). For example, the gNB may configure the UE to perform thefirst UL data transmission. Also, for example, the gNB may configure theUE to perform the second UL data transmission. And, in a case that theUE is configured with the first UL data transmission and/or the secondUL data transmission, the UE may perform the first UL data transmissionand/or the second UL data transmission (e.g., by using the first PUSCHand/or the second PUSCH).

Namely, in the certain timing where the second PUSCH is scheduled, ifthe first PUSCH is scheduled in the certain timing, the first UL grantmay override the second PUSCH for the certain timing. And, the UE mayperform the first UL data transmission and/or the second UL datatransmission using the first PUSCH in the certain timing. Also, in thecertain timing where the first PUSCH is scheduled, if the second PUSCHis scheduled in the certain timing, the second UL grant may override thesecond PUSCH for the certain timing. And, the UE may perform the firstUL data transmission and/or the second UL data transmission using thesecond PUSCH in the certain timing. Also, the gNB may transmit (e.g., byusing the RRC message) information used for configuring which PUSCH isused (e.g., which PUSCH is prioritized) for the UL data transmission(e.g., the first UL data transmission and/or the second UL datatransmission). For example, the gNB may configure the UE to use thefirst PUSCH. Also, for example, the gNB may configure the UE to use thesecond PUSCH. And, in a case that the UE is configured with the firstPUSCH, the UE may perform the first UL data transmission and/or thesecond UL data transmission using the first PUSCH. Also, in a case thatthe UE is configured with the second PUSCH, the UE may perform the firstUL data transmission and/or the second UL data transmission using thesecond PUSCH.

Here, as one example, the case where the first UL data transmission(i.e., the first PUSCH) and the second UL data transmission (i.e., thesecond PUSCH) is described above. However, the descriptions may beapplied to all combination(s) of the first UL data transmission (i.e.,the first PUSCH), the second UL data transmission (i.e., the secondPUSCH), the third UL data transmission (i.e., the third PUSCH), and/orthe fourth UL data transmission (i.e., the fourth PUSCH). Namely, forexample, the above descriptions may be applied to the first UL datatransmission (i.e., the first PUSCH) and the third UL data transmission(i.e., the third PUSCH). Namely, the second UL data transmission may bereplaced by the third UL data transmission, and the second PUSCH may bereplaced by the third PUSCH. Also, for example, the above descriptionsmay be applied to the first UL data transmission (i.e., the first PUSCH)and the fourth UL data transmission (i.e., the fourth PUSCH). Namely,the second UL data transmission may be replaced by the fourth UL datatransmission, and the second PUSCH may be replaced by the fourth PUSCH.Also, for example, the above descriptions may be applied to the secondUL data transmission (i.e., the second PUSCH) and the third UL datatransmission (i.e., the third PUSCH). Namely, the first UL datatransmission may be replaced by the second UL data transmission, thefirst PUSCH may be replaced by the second PUSCH, the second UL datatransmission may be replaced by the third UL data transmission, and thesecond PUSCH may be replaced by the third PUSCH. Also, for example, theabove descriptions may be applied to the second UL data transmission(i.e., the second PUSCH) and the fourth UL data transmission (i.e., thefourth PUSCH). Namely, the first UL data transmission may be replaced bythe second UL data transmission, the first PUSCH may be replaced by thesecond PUSCH, the second UL data transmission may be replaced by thefourth UL data transmission, and the second PUSCH may be replaced by thefourth PUSCH. Also, for example, the above descriptions may be appliedto the third UL data transmission (i.e., the third PUSCH) and the fourthUL data transmission (i.e., the fourth PUSCH). Namely, the first UL datatransmission may be replaced by the third UL data transmission, thefirst PUSCH may be replaced by the third PUSCH, the second UL datatransmission may be replaced by the fourth UL data transmission, and thesecond PUSCH may be replaced by the fourth PUSCH.

As described above, the UE may monitor one or more search spaces. Thesearch space may be treated as a set of PDCCH candidates. Examples ofsearch spaces that may be utilized in accordance with the systems andmethods disclosed herein are given as follows. One example is the commonsearch space. The common search space may contain some informationrelated to URLLC. Another example is the UE-specific search space. Insome approaches, there may be no URLLC-specific search space, or URLLCmay share the same UE-specific search space with other services. Toobtain URLLC related information, the UE may search the UE-specificsearch space by using the URLLC C-RNTI (if implemented, for example) orthe C-RNTI/the SPS C-RNTI (if no URLLC-specific RNTI is implemented, forexample). Yet another example is a URLLC search space. The URLLC mayhave a specific search space, which may be referred to as a URLLC searchspace (as an example, the specification may use a different name, forinstance). The UE may obtain URLLC related information by searching theURLLC search space. In other examples, any combination of the abovesearch spaces may be implemented and/or used.

Namely, as described above, for example, the search space (e.g., theUSS) may be composed of CCEs having numbers that are determined based onthe RNTI(s), the slot number in the radio frame, the aggregation level,and/or the like. Here, the search space determined based on the RNTI(s),the slot number in the radio frame, the aggregation level, and/or thelike may include the CSS. Namely, the search space may be given by theRNTI(s). For example, a first search space (e.g., a first USS and/or afirst CSS) given by the RNTI “A” may be defined. Also, a second searchspace (e.g., a second USS and/or a second CSS) given by the RNTI “B” maydefined. Also, a third search space (e.g., a third USS and/or a thirdCSS) given by the RNTI “C” may be defined.

For example, the UE may monitor the first UL grant in the search spacegiven by the RNTI “A.” For example, the UE may monitor the first ULgrant in the search space given by the RNTI “A” on the primary celland/or secondary cell. Also, the UE may monitor the first UL grant inthe search space given by the RNTI “B.” Also, the UE may monitor thefirst UL grant in the search space given by the RNTI “C.” For example,the UE may monitor the first UL grant in the search space given by theRNTI “C” on the primary cell and secondary cell.

Also, the UE may monitor the second UL grant in the search space givenby the RNTI “A.” For example, the UE may monitor the second UL grant inthe search space given by the RNTI “A” only on the primary cell. Also,the UE may monitor the second UL grant in the search space given by theRNTI “B.” For example, the UE may monitor the second UL grant in thesearch space given by the RNTI “B” only on the primary cell. Also, theUE may monitor the second UL grant in the search space given by the RNTI“C.”

Also, the UE may monitor the third UL grant in the search space given bythe RNTI “A.” For example, the UE may monitor the third UL grant in thesearch space given by the RNTI “A” on the primary cell and/or thesecondary cell. Also, the UE may monitor the third UL grant in thesearch space given by the RNTI “B.” For example, the UE may monitor thethird UL grant in the search space given by the RNTI “B” on the primarycell and/or the secondary cell. Also, the UE may monitor the third ULgrant in the search space given by the RNTI “B” only on the primarycell. Also, the UE may monitor the third UL grant in the search spacegiven by the RNTI “C.” For example, the UE may monitor the third ULgrant in the search space given by the RNTI “C” on the primary celland/or the secondary cell. Here, the gNB may transmit, (e.g., by usingthe RRC message), information used for configuring the secondary cell onwhich the UE monitors the third UL grant (e.g., in the search space(i.e., the USS and/or the CSS)). Also, the gNB may transmit (e.g., byusing the RRC message), information used for configuring a position(s)of timing (e.g., a subframe, a slot, a sub-slot (i.e., a mini-slot),and/or a symbol, i.e., occasion(s)) in which the UE monitors the thirdUL grant (e.g., in the search space (i.e., the USS and/or the CSS)).

Also, the UE may monitor the fourth UL grant in the search space givenby the RNTI “A.” For example, the UE may monitor the fourth UL grant inthe search space given by the RNTI “A” on the primary cell and/or thesecondary cell. For example, the UE may monitor the fourth UL grant inthe search space given by the RNTI “B” on the primary cell and/or thesecondary cell. Also, the UE may monitor the fourth UL grant in thesearch space given by the RNTI “B” only on the primary cell. Also, theUE may monitor the fourth UL grant in the search space given by the RNTI“C.” For example, the UE may monitor the fourth UL grant in the searchspace given by the RNTI “C” on the primary cell and/or the secondarycell. Here, the gNB may transmit, (e.g., by using the RRC message),information used for configuring the secondary cell on which the UEmonitors the fourth UL grant (e.g., in the search space (i.e., the USSand/or the CSS)). Also, the gNB may transmit (e.g., by using the RRCmessage), information used for configuring a position(s) of timing(e.g., a subframe, a slot, a sub-slot (i.e., a mini-slot), and/or asymbol, i.e., occasion(s)) in which the UE monitors the fourth UL grant(e.g., in the search space (i.e., the USS and/or the CSS)).

Here, the gNB may transmit (e.g., by using the RRC message) information(e.g., first information) used for configuring (e.g., indicating) thesearch space(s) (e.g., a position(s) of the search space). For example,the gNB may transmit information used for configuring the searchspace(s) (e.g., the USS and/or the CSS) in which the UE monitors the ULgrant with the RNTI “A.” Namely, the UE may monitor the first UL grant(e.g., the first UL grant with the C-RNTI (i.e., the RNTI “A”)) in theconfigured position(s) of the search space(s). Also, the UE may monitorthe third UL grant (e.g., the third UL grant with the C-RNTI (i.e., theRNTI “A”)) in the configured position(s) of the search space(s). Also,the UE may monitor the fourth UL grant (e.g., the fourth UL grant withthe C-RNTI (i.e., the RNTI “A”)) in the configured position(s) of thesearch space(s). Here, the second UL grant (e.g., the second UL grantwith the SPS C-RNTI (i.e., the RNTI “B”)) may be monitored in theconfigured position(s) of the search space(s). For example, the UE maymonitor the second UL grant (e.g., the second UL grant with the SPSC-RNTI (i.e., the RNTI “B”)) in the same search space(s) as the searchspace(s) in which the UE monitors the first UL grant (e.g., the first ULgrant with the C-RNTI (i.e., the RNTI “A”)).

Also, for example, the gNB may transmit, (e.g., by using the RRCmessage), information (e.g., second information) used for configuringthe search space(s) (e.g., the USS and/or the CSS) in which the UEmonitors the UL grant with the RNTI “B.” For example, the gNB maytransmit, (e.g., by using the RRC message), information (e.g., thesecond information) as a part of the SPS configuration (e.g., theconfiguration of the interval (e.g., the subframe and/or slot basedinterval of the semi-persistent scheduling)). Namely, the UE may monitorthe second UL grant (e.g., the second UL grant with the SPS C-RNTI(i.e., the RNTI “B”)) in the configured position(s) of the searchspace(s). Also, the UE may monitor the third UL grant (e.g., the thirdUL grant with the SPS C-RNTI (i.e., the RNTI “B”)) in the configuredposition(s) of the search space(s). Also, the UE may monitor the fourthUL grant (e.g., the fourth UL grant with the SPS C-RNTI (i.e., the RNTI“B”)) in the configured position(s) of the search space(s).

Also, for example, the gNB may transmit, (e.g., by using the RRCmessage), information (e.g., third information) used for configuring thesearch space(s) (e.g., the USS and/or the CSS) in which the UE monitorsthe UL grant with the RNTI “C.” For example, the gNB may transmit,(e.g., by using the RRC message), information (e.g., the thirdinformation) as a part of the SPS configuration (e.g., the configurationof the interval of semi-persistent scheduling (e.g., the slot, thesub-slot (i.e., the mini-slot) and/or the symbol based interval ofsemi-persistent scheduling). Namely, the UE may monitor the third ULgrant (e.g., the third UL grant with the URLLC C-RNTI (i.e., the RNTI“C”)) in the configured position(s) of the search space(s). Also, the UEmay monitor the fourth UL grant (e.g., the fourth UL grant with theURLLC C-RNTI (i.e., the RNTI “C”)) in the configured position(s) of thesearch space(s).

In some approaches, resource sharing may be performed between differenttransmissions. For example, any resource may be used by any kind oftransmission. For example, the sharing of the PUSCH resource for thesecond UL data transmission, the third UL data transmission, and/or thefourth UL data transmission may be utilized. In some approaches, eachkind of transmission may use its own dedicated resource so that there isno conflict (i.e., non-contention based UL transmission, contention-freeUL transmission). In some approaches, different transmissions may sharethe same resource for efficiency (i.e., contention based ULtransmission). Some kinds of resource sharing are described as follows.

Inter-service resource sharing is one kind of resource sharing. Asdescribed above, URLLC may coexist with other services (e.g., eMBB). Dueto a latency requirement, URLLC may have the highest priority. Someexamples of inter-service resource sharing are given as follows.Grant-based URLLC (e.g., the third UL data transmission (i.e., the thirdPUSCH)) and grant-based eMBB (e.g., the first UL data transmission(i.e., the first PUSCH)) may be one example of inter-service resourcesharing. If a time delay between UL grant reception in DL and UL data(PUSCH) transmission is the same for both services, the coexistenceissue may be solved by gNB/eNB scheduling. The UL grant for URLLC (e.g.,the third UL grant and/or the fourth UL grant) and the UL grant for eMBB(e.g., the first UL grant) may indicate different frequency resources(e.g., different resource blocks) or different time resources (e.g.,different mini-slots/OFDM symbols within the slot/subframe). Ratematching and/or puncturing may be used for eMBB (e.g., the first ULdata) to protect URLLC data (e.g., the third UL data, and/or the fourthUL data). Namely, as described above, in a case that the first UL datatransmission and the third UL data transmission would occur in thecertain timing, the rate mating and/or the puncturing may be used forthe first UL data, and the UE may transmit the first data and the thirddata in the certain timing. Also, as described above, in a case that thefirst UL data transmission and the fourth UL data transmission wouldoccur in the same timing, the rate matching and/or the puncturing may beused for the first UL data, and the UE may transmit the first UL dataand the fourth UL data in the certain timing. In some approaches, thegNB/eNB may not send an UL grant for an eMBB (e.g., the first UL grant)to the UE if the gNB/eNB sends UL grant for URLLC (e.g., the third ULgrant and/or the fourth UL grant) to that UE (or a different UE) at thesame timing, so that possible resource overlapping/conflict can beavoided.

If a time delay between UL grant reception in DL and UL datatransmission is shorter for URLLC due to the latency requirement, aresource may already be allocated by an earlier UL grant for the eMBBservice when the gNB/eNB sends an UL grant for URLLC service, which mayuse the same resource or part(s) of the same resource. In some cases,the gNB/eNB may send the UL grant to indicate a different resource(e.g., a different frequency resource or a different time resource) forURLLC. In some cases, the gNB/eNB may send the UL grant for URLLC (e.g.,the third UL grant and/or the fourth UL grant) to preempt (e.g.,puncture or superpose) the resource which is already granted for eMBB(e.g., scheduled by using the first UL grant). Since both services aregrant-based, no extra indication may be needed for decoding at thegNB/eNB.

Grant-free URLLC (e.g., the fourth UL data transmission (i.e., thefourth PUSCH)) and grant-based eMBB (e.g., the first UL datatransmission (i.e., the first PUSCH)) may be another example ofinter-service resource sharing. The grant-free URLLC resource (e.g., thefourth PUSCH) may be pre-configured. For example, a frequency resourceand/or a time resource of the fourth PUSCH may be configured by usingthe RRC message. Also, the time resource of the fourth PUSCH may beconfigured by using the RRC message and the frequency resource of thefourth PUSCH may be indicated by using the fourth UL grant. When the UEhas URLLC data, the UE may transmit at the configured resource. Thegrant-based eMBB may avoid a configured grant-free URLLC resource, whichmeans the configured resource may be dedicated for URLLC. However, aURLLC UE may skip the configured resource if there is no URLLC data. Ina different approach, to enhance the resource utilization efficiency,grant-based eMBB (e.g., the first PUSCH) may be allowed to use aconfigured URLLC resource (e.g., the third UL data transmission and/orthe fourth UL data transmission). If a configured URLLC resource isgranted for eMBB (e.g., if the first PUSCH is scheduled in the certaintiming where the third PUSCH and/or the fourth PUSCH is scheduled), butthe UE has URLLC data (e.g., the third UL data and/or the fourth ULdata) to transmit at the configured resource, URLLC data (e.g., thethird UL data and/or the fourth UL data) may preempt the eMBB service(e.g., the first PUSCH). Namely, for example, the UE may transmit thefirst UL data and the third UL data using the first PUSCH. Also, forexample, the UE may transmit the first UL data and the fourth UL datausing the first PUSCH. Here, the UE may just abandon (e.g., give up,drop, withdraw, postpone) the eMBB transmission (e.g., the first UL datatransmission). And, the UE may transmit only the third data using thefirst PUSCH. An indication may be used to indicate the presence of URLLCdata (e.g., the third UL data and/or the fourth UL data) in the firstPUSCH. And, the indication used to indicate the present of URLLC datamay be used for helping the gNB/eNB decoding. Also, the gNB/eNB mayassume that there is URLLC data at the configured resource and blinddecode the URLLC data first.

Grant-free URLLC (e.g., the fourth UL data transmission (i.e., thefourth PUSCH)) and grant-free eMBB and/or SPS (e.g., the second UL datatransmission (i.e., the second PUSCH)) may be another example ofinter-service resource sharing. The URLLC resource (e.g., the fourthPUSCH) and the eMBB resource (e.g., the second PUSCH) may be orthogonalto each other by configuration. Namely, the gNB may transmit, (by usingthe RRC message and/or the DCI (e.g., the DCI for activating the SPS)),information used for configuring the orthogonal (e.g., OCC (orthogonalcover code) for the PUSCH(s) (e.g., the fourth PUSCH and/or the secondPUSCH)). However, if overlapping exists, the URLLC resource may overridethe eMBB resource.

Grant-based URLLC (e.g., the third UL data transmission (i.e., the thirdPUSCH)) and grant-free eMBB and/or SPS (e.g., the second UL datatransmission (i.e., the second PUSCH)) may be another example ofinter-service resource sharing. Grant-based URLLC may overridegrant-free eMBB.

Also, examples of intra-URLLC resource sharing are given as follows.Grant-based initial transmission (e.g., the first UL data transmission(i.e., the first PUSCH), and/or the third UL data transmission (i.e.,the third PUSCH)) and grant-free initial transmission (e.g., the secondUL data transmission (i.e., the second PUSCH), and/or the fourth UL datatransmission (i.e., the fourth PUSCH)) may be an example ofintra-service resource sharing. Grant-based initial transmission mayoverride grant-free initial transmission. Namely, in a case that theGrant-based initial transmission and the grant-free initial transmissionwould occur in the certain timing, the UE may perform the Grant-basedinitial transmission in the certain timing. Namely, in the certaintiming where the PUSCH (e.g., the second PUSCH and/or the fourth PUSCH)for the grant-free initial transmission is scheduled, if the PUSCH(e.g., the first PUSCH and/or the third PUSCH) for the Grant-basedinitial transmission is scheduled, the UL grant for the Grant-basedinitial transmission (e.g., the first UL grant and/or the third ULgrant) may override the UL grant for the grant-free initial transmission(e.g., the second UL grant and/or the fourth grant).

Grant-based retransmission (e.g., the first UL data transmission (i.e.,the first PUSCH), and/or the third UL data transmission (i.e., the thirdPUSCH)) and grant-free initial transmission (e.g., the second UL datatransmission (i.e., the second PUSCH), and/or the fourth UL datatransmission (i.e., the fourth PUSCH)) may be another example ofintra-service resource sharing. Here, the Grant-based retransmission maybe a grant-based repetition(s) (i.e., the third UL data transmission(i.e., the third PUSCH)). The Grant-based retransmission may avoid aconfigured grant-free resource. Grant-based retransmission may overridegrant-free initial transmission. Namely, in a case that the Grant-basedretransmission and the grant-free initial transmission would occur inthe certain timing, the UE may perform the Grant-based retransmission inthe certain timing. Namely, in the certain timing where the PUSCH (e.g.,the second PUSCH and/or the fourth PUSCH) for the grant-free initialtransmission is scheduled, if the PUSCH (e.g., the first PUSCH and/orthe third PUSCH) for the Grant-based retransmission is scheduled, the ULgrant for the Grant-based retransmission (e.g., the first UL grantand/or the third UL grant) may override the UL grant for the grant-freeinitial transmission (e.g., the second UL grant and/or the fourthgrant). In another design, grant-free initial transmission may overridegrant-based retransmission. Namely, in a case that the Grant-basedretransmission and the grant-free initial transmission would occur inthe certain timing, the UE may perform the grant-free initialtransmission in the certain timing. Namely, in the certain timing wherethe PUSCH (e.g., the second PUSCH and/or the fourth PUSCH) for thegrant-free initial transmission is scheduled, if the PUSCH (e.g., thefirst PUSCH and/or the third PUSCH) for the Grant-based retransmissionis scheduled, the UL grant for the grant-free initial transmission(e.g., the second UL grant and/or the fourth UL grant) may override theUL grant for the Grant-based retransmission (e.g., the first UL grantand/or the third grant).

Grant-free initial transmission (e.g., the second UL data transmission(i.e., the second PUSCH) and/or the fourth UL data transmission (i.e.,the fourth PUSCH)) and grant-free retransmission (e.g., the second ULdata transmission (i.e., the second PUSCH) and/or the fourth UL datatransmission (i.e., the fourth PUSCH)) may be another example ofintra-service resource sharing. Here, the grant-free retransmission maybe a grant-free repetition(s) (i.e., the fourth UL data transmission(i.e., the fourth PUSCH)). Grant-free retransmission may overridegrant-free initial transmission. Namely, in a case that the grant-freeinitial transmission and the grant-free retransmission would occur inthe certain timing, the UE may perform the grant-free retransmission inthe certain timing. Namely, in the certain timing where the PUSCH (e.g.,the second PUSCH and/or the fourth PUSCH) for the grant-freeretransmission is scheduled, if the PUSCH (e.g., the second PUSCH and/orthe fourth PUSCH) for the grant-free initial transmission is scheduled,the UL grant for the grant-free retransmission (e.g., the second ULgrant and/or the fourth UL grant) may override the UL grant for thegrant-free initial transmission (e.g., the second UL grant and/or thefourth grant). In another design, grant-free initial transmission mayoverride grant-free retransmission. Namely, in a case that thegrant-free initial transmission and the grant-free retransmission wouldoccur in the certain timing, the UE may perform the grant-free initialtransmission in the certain timing. Namely, in the certain timing wherethe PUSCH (e.g., the second PUSCH and/or the fourth PUSCH) for thegrant-free retransmission is scheduled, if the PUSCH (e.g., the secondPUSCH and/or the fourth PUSCH) for the grant-free initial transmissionis scheduled, the UL grant for the grant-free initial transmission(e.g., the second UL grant and/or the fourth UL grant) may override theUL grant for the grant-free retransmission transmission (e.g., thesecond UL grant and/or the fourth grant).

Grant-based retransmission (e.g., the first UL data transmission (i.e.,the first PUSCH) and/or the third UL data transmission (i.e., the thirdPUSCH)) and grant-free retransmission (e.g., the second UL datatransmission (i.e., the second PUSCH) and/or the fourth UL datatransmission (i.e., the fourth PUSCH)) may be another example ofintra-service resource sharing. Here, the grant-free retransmission maybe a grant-free repetition(s) (i.e., the fourth UL data transmission(i.e., the fourth PUSCH)). Grant-based retransmission may overridegrant-free retransmission. Namely, in a case that the Grant-basedretransmission and the grant-free retransmission would occur in thecertain timing, the UE may perform the Grant-based retransmission in thecertain timing. Namely, in the certain timing where the PUSCH (e.g., thesecond PUSCH and/or the fourth PUSCH) for the grant-free retransmissionis scheduled, if the PUSCH (e.g., the first PUSCH and/or the thirdPUSCH) for the Grant-based retransmission is scheduled, the UL grant forthe Grant-based retransmission (e.g., the first UL grant and/or thethird UL grant) may override the UL grant for the grant-freeretransmission transmission (e.g., the second UL grant and/or the fourthgrant).

Some approaches for hybrid automatic repeat request (HARQ) processes aredescribed as follows. HARQ processes coexistence is one aspect of HARQprocesses. In some approaches, URLLC may share HARQ processes with otherservices. For example, a same HARQ process may be used by either URLLCservice or a different service (e.g., eMBB).

In some approaches, URLLC may use dedicated HARQ processes. For example,a URLLC service may have its own HARQ processes, which may be separatedfrom other services.

HARQ process timing and number is another aspect of HARQ processes. Insome approaches, synchronous HARQ may be used. For example, the timingbetween two adjacent transmissions in a HARQ process may be fixed. TheHARQ process ID may be derived from the TTI (subframe/slot/mini-slot/OS)index.

In some approaches, asynchronous HARQ may be used. For example, thetiming between two adjacent transmissions in a HARQ process may bedynamic. A HARQ process ID may be explicitly indicated.

In some approaches, a combination or enhancement of the above HARQprocedures may be implemented. For example, different services may usedifferent types of HARQ procedures. Different types of transmissions mayuse different types of HARQ procedures. For instance, a URLLC servicemay use synchronous HARQ while eMBB service may use asynchronous HARQ;an initial transmission may use synchronous HARQ while retransmissionmay use asynchronous HARQ.

For example, the gNB may transmit, (by using the RRC message),information used for configuring multiple HARQ process IDs. For example,the gNB may configure the first HARQ process ID associated with thesecond UL grant (e.g., the first HARQ process ID corresponding to thesecond UL grant). Also, the gNB may configure a second HARQ process IDassociated with the fourth UL grant (e.g., the second HARQ process IDcorresponding to the fourth UL grant). Also, the gNB may configure athird HARQ process ID associated with the third UL grant (e.g., thethird HARQ process ID corresponding to the third UL grant). As describedabove, the second UL grant may be the UL grant with the RNTI “B” (e.g.,the SPS C-RNTI). Also, the fourth UL grant may be the UL grant with theRNTI “B” (e.g., the SPS C-RNTI). Also, the third UL grant may be the ULgrant with the RNTI “B” (e.g., the SPS C-RNTI). Also, the fourth ULgrant may be the UL grant with the RNTI “A” (e.g., the C-RNTI). Also,the third UL grant may be the UL grant with the RNTI “A” (e.g., theC-RNTI).

Namely, for example, in a case that the second UL grant including thefirst HARQ process ID is received (i.e., based on a detection of thesecond UL grant including the first HARQ process ID), the UE may performthe UL data transmission (e.g., the second UL data transmission). Here,the UL data transmission (e.g., the second UL data transmission) maycorrespond to the first HARQ process ID. Also, in a case that the fourthUL grant including the second HARQ process ID is received (i.e., basedon a detection of the fourth UL grant including the second HARQ processID), the UE may perform the UL data transmission (e.g., the fourth ULdata transmission). Here, the UL data transmission (e.g., the fourth ULdata transmission) may correspond to the second HARQ process ID. Also,in a case that the third UL grant including the third HARQ process ID isreceived (i.e., based on a detection of the third UL grant including thethird HARQ process ID), the UE may perform the UL data transmission(e.g., the third UL data transmission). Here, the UL data transmission(e.g., the third UL data transmission) may correspond to the third HARQprocess ID.

Also, the gNB may configure the fourth HARQ process ID associated withthe RNTI “A” (e.g., the fourth HARQ process ID corresponding to the RNTI“A”). Also, the gNB may configure the fifth HARQ process ID associatedwith the RNTI “B” (e.g., the fifth HARQ process ID corresponding to theRNTI “B”). Also, the gNB may configure the sixth HARQ process IDassociated with the RNTI “C” (e.g., the sixth HARQ process IDcorresponding to the RNTI “C”). As described above, the second UL grantmay be the UL grant with the RNTI “B” (e.g., the SPS C-RNTI). Also, thethird UL grant may be the UL grant with the RNTI “A” (e.g., the C-RNTI).Also, the third UL grant may be the UL grant with the RNTI “C” (e.g.,the URLLC C-RNTI). Also, the fourth UL grant may be the UL grant withthe RNTI “B” (e.g., the SPS C-RNTI). Also, the fourth UL grant may bethe UL grant with the RNTI “C” (e.g., the URLLC C-RNTI).

Namely, for example, in a case that the UL grant with the RNTI “A” isreceived (i.e., based on a detection of the UL grant with the RNTI “A”),the UE may perform the UL data transmission (e.g., the third UL datatransmission). Here, the UL data transmission (e.g., the third UL datatransmission) may correspond to the fourth HARQ process ID. Also, in acase that the UL grant with the RNTI “B” is received (i.e., based on adetection of the UL grant with the RNTI “B”), the UE may perform the ULdata transmission (e.g., the second UL data transmission, the third ULdata transmission, and/or the fourth UL data transmission). Here, the ULdata transmission (e.g., the second UL data transmission, the third ULdata transmission, and/or the fourth UL data transmission) maycorrespond to the fifth HARQ process ID. Also, in a case that the ULgrant with the RNTI “C” is received (i.e., based on a detection of theUL grant with the RNTI “C”), the UE may perform the UL data transmission(e.g., the third UL data transmission and/or the fourth UL datatransmission). Here, the UL data transmission (e.g., the third UL datatransmission and/or the fourth UL data transmission) may correspond tothe sixth HARQ process ID.

Also, the HARQ process ID may be determined based on a timing (e.g., asubframe, a slot, a sub-slot, and/or a symbol) in which the UL datainitial transmission (e.g., the first UL data initial transmission, thesecond UL data initial transmission, the third UL data initialtransmission, and/or the fourth UL data initial transmission) isperformed. For example, the HARQ process ID may be determined based onan index of the timing in which the UL data initial transmission isperformed. Additionally, the gNB may transmit, (by using the RRC messageand/or the DCI (e.g., the DCI for activating the SPS)), information usedfor determining the HARQ process ID. Namely, for example, the UE maydetermine the HARQ process ID based on the timing and the information(i.e., the information used for determining the HARQ process) which istransmitted by the gNB. For example, a function (e.g., an equation) maybe defined for determining the HARQ process ID. Namely, for example, thetiming (i.e., the index of the timing) and the information transmittedby the gNB (i.e., a value of the information) may be used as parametersfor calculating (i.e., determining) the HARQ process ID based on thefunction (e.g., the equation).

Various examples of the systems and methods disclosed herein are nowdescribed with reference to the Figures, where like reference numbersmay indicate functionally similar elements. The systems and methods asgenerally described and illustrated in the Figures herein could bearranged and designed in a wide variety of different implementations.Thus, the following more detailed description of severalimplementations, as represented in the Figures, is not intended to limitscope, as claimed, but is merely representative of the systems andmethods.

FIG. 1 is a block diagram illustrating one implementation of one or moregNBs 160 and one or more UEs 102 in which systems and methods forultra-reliable and low-latency communication operations may beimplemented. The one or more UEs 102 communicate with one or more gNBs160 using one or more antennas 122 a-n. For example, a UE 102 transmitselectromagnetic signals to the gNB 160 and receives electromagneticsignals from the gNB 160 using the one or more antennas 122 a-n. The gNB160 communicates with the UE 102 using one or more antennas 180 a-n.

The UE 102 and the gNB 160 may use one or more channels 119, 121 tocommunicate with each other. For example, a UE 102 may transmitinformation or data to the gNB 160 using one or more uplink channels121. Examples of uplink channels 121 include a PUCCH (Physical UplinkControl Channel) and a PUSCH (Physical Uplink Shared Channel), PRACH(Physical Random Access Channel), etc. For example, uplink channels 121(e.g., PUSCH) may be used for transmitting UL data (i.e., TransportBlock(s), MAC PDU, and/or UL-SCH (Uplink-Shared Channel)).

Here, UL data may include URLLC data. The URLLC data may be UL-SCH data.Here, URLLC-PUSCH (i.e., a different Physical Uplink Shared Channel fromPUSCH) may be defined for transmitting the URLLC data. For the sake ofsimple description, the term “PUSCH” may mean any of (1) only PUSCH(e.g., regular PUSCH, non-URLLC-PUSCH, etc.), (2) PUSCH or URLLC-PUSCH,(3) PUSCH and URLLC-PUSCH, or (4) only URLLC-PUSCH (e.g., not regularPUSCH).

Also, for example, uplink channels 121 may be used for transmittingHybrid Automatic Repeat Request-ACK (HARQ-ACK), Channel StateInformation (CSI), and/or Scheduling Request (SR). The HARQ-ACK mayinclude information indicating a positive acknowledgment (ACK) or anegative acknowledgment (NACK) for DL data (i.e., Transport Block(s),Medium Access Control Protocol Data Unit (MAC PDU), and/or DL-SCH(Downlink-Shared Channel)).

The CSI may include information indicating a channel quality ofdownlink. The SR may be used for requesting UL-SCH (Uplink-SharedChannel) resources for new transmission and/or retransmission. Namely,the SR may be used for requesting UL resources for transmitting UL data.

The one or more gNBs 160 may also transmit information or data to theone or more UEs 102 using one or more downlink channels 119, forinstance. Examples of downlink channels 119 include a PDCCH, a PDSCH,etc. Other kinds of channels may be used. The PDCCH may be used fortransmitting Downlink Control Information (DCI).

Each of the one or more UEs 102 may include one or more transceivers118, one or more demodulators 114, one or more decoders 108, one or moreencoders 150, one or more modulators 154, a data buffer 104 and a UEoperations module 124. For example, one or more reception and/ortransmission paths may be implemented in the UE 102. For convenience,only a single transceiver 118, decoder 108, demodulator 114, encoder 150and modulator 154 are illustrated in the UE 102, though multipleparallel elements (e.g., transceivers 118, decoders 108, demodulators114, encoders 150 and modulators 154) may be implemented.

The transceiver 118 may include one or more receivers 120 and one ormore transmitters 158. The one or more receivers 120 may receive signalsfrom the gNB 160 using one or more antennas 122 a-n. For example, thereceiver 120 may receive and downconvert signals to produce one or morereceived signals 116. The one or more received signals 116 may beprovided to a demodulator 114. The one or more transmitters 158 maytransmit signals to the gNB 160 using one or more antennas 122 a-n. Forexample, the one or more transmitters 158 may upconvert and transmit oneor more modulated signals 156.

The demodulator 114 may demodulate the one or more received signals 116to produce one or more demodulated signals 112. The one or moredemodulated signals 112 may be provided to the decoder 108. The UE 102may use the decoder 108 to decode signals. The decoder 108 may producedecoded signals 110, which may include a UE-decoded signal 106 (alsoreferred to as a first UE-decoded signal 106). For example, the firstUE-decoded signal 106 may comprise received payload data, which may bestored in a data buffer 104. Another signal included in the decodedsignals 110 (also referred to as a second UE-decoded signal 110) maycomprise overhead data and/or control data. For example, the secondUE-decoded signal 110 may provide data that may be used by the UEoperations module 124 to perform one or more operations.

In general, the UE operations module 124 may enable the UE 102 tocommunicate with the one or more gNBs 160. The UE operations module 124may include a UE URLLC module 126.

The UE URLLC module 126 may perform URLLC operations. In someapproaches, URLLC operations may include grant-free data transmission(e.g., UL transmission without detection of downlink control informationfor triggering), sub-slot (sub-slot may be also referred to asmini-slot) based data transmission, SR triggered data transmission (SRis sent before data transmission), and/or SR-less data transmission (SRis not used), etc.

A UE with URLLC capability may support different types of resources. ForURLLC uplink (UL) transmission schemes (including repetition), at leastsemi-static resource (re-)configuration may be supported. In LTE,semi-persistent scheduling (SPS) is a regular way for semi-staticresource allocation. There are several basic procedures for SPS: radioresource control (RRC) configuration (e.g., a RRC message, a RRCsignal), activation, UL transmission and/or deactivation. The RRCconfiguration may be exchanged between the eNB/gNB 160 and the UE 102through a RRC layer. The RRC signal may be included in a higher layersignal. At the beginning, the eNB/gNB 160 may allocate an SPS resource(e.g., periodicity of the SPS resource) and function to a specific UE102 by SPS-Config, which is shown in the SPS-Config information elementof Listing-1. Here, for example, the eNB/gNB 160 may configure aperiodicity (e.g., a time resource) by using the RRC signal, andindicate the SPS resource (e.g., a frequency resource) by using a DCIformat.

Listing-1 -- ASN1START SPS-Config ::= SEQUENCE {  semiPersistSchedC-RNTI C-RNTI OPTIONAL, -- Need OR   sps-ConfigDLSPS-ConfigDL OPTIONAL, -- Need ON   sps-ConfigUL SPS-ConfigUL OPTIONAL-- Need ON } SPS-ConfigDL ::= CHOICE{   release NULL,   setup SEQUENCE {    semiPersistSchedIntervalDL ENUMERATED { sf10, sf20, sf32, sf40,sf64, sf80, sf128, sf160, sf320, sf640, spare6, spare5, spare4, spare3,spare2, spare1},     numberOfConfSPS-Processes INTEGER (1..8),    n1PUCCH-AN-PersistentList N1PUCCH-AN-PersistentList,     ...,    [[ twoAntennaPortActivated-r10 CHOICE {       release NULL,      setup SEQUENCE {        n1PUCCH-AN-PersistentListP1-r10 N1PUCCH-AN- PersistentList      }      }   OPTIONAL -- Need ON     ]]   } } SPS-ConfigUL ::=CHOICE {   release NULL,   setup SEQUENCE {    semiPersistSchedIntervalUL ENUMERATED {-- Period of UL SPS sf10,sf20, sf32, sf40, sf64, sf80, sf128, sf160, sf320, sf640, sf1-v14xy,sf2-v14xy, sf3-v14xy, sf4-v14xy, sf5-v14xy, spare1},    implicitReleaseAfter ENUMERATED {e2, e3, e4, e8},     p0-PersistentSEQUENCE {       p0-NominalPUSCH-Persistent INTEGER (−126..24),      p0-UE-PUSCH-Persistent INTEGER (−8..7)     }  OPTIONAL, -- Need OP    twoIntervalsConfig ENUMERATED {true}   OPTIONAL, -- Cond TDD    ...,     [[ p0-PersistentSubframeSet2-r12 CHOICE {        releaseNULL,        setup SEQUENCE {        p0-NominalPUSCH-PersistentSubframeSet2-r12   INTEGER (−126..24),        p0-UE-PUSCH-PersistentSubframeSet2-r12   INTEGER (−8..7)       }    } OPTIONAL -- Need ON     ]],     [[ numberOfConfUlSPS-Processes-r13INTEGER (1..8)   OPTIONAL -- Need OR     ]]   } }N1PUCCH-AN-PersistentList ::= SEQUENCE (SIZE (1..4)) OF INTEGER(0..2047) -- ASN1STOP

The UE 102 may use an SPS resource for a grant-free URLLC ULtransmission. Additionally or alternatively, the eNB/gNB 160 mayallocate a URLLC-specific grant-free resource for URLLC UL transmission.For example, the eNB/gNB 160 may allocate an SPS-like resource, which isshown in the URLLC-Config information element of Listing 2. Here,without loss of generality, the URLLC-specific grant-free resource maybe referred to as a “URLLC-SPS resource” and the corresponding schememay be referred to as “URLLC-SPS.”

Listing-2 -- ASN1START URLLC-Config ::= SEQUENCE {   URLLCSchedC-RNTIC-RNTI (or URLLC C-RNTI)   OPTIONAL, -- Need OR   URLLC-ConfigULURLLC-ConfigUL OPTIONAL } URLLC-ConfigUL ::= CHOICE {   release NULL,  setup SEQUENCE {     URLLCInterval ENUMERATED {-- Period of UL SPSslot1, slot2, slot4, slot8, slot10, slot20, slot32, slot40, slot64,slot80, slot128, slot160, slot320, slot640},      numberOfRepetitionENUMERATED {-- Number of UL Repetitions 1, 2, 4, 8},     numberOfConfURLLC-Processes INTEGER (1..8),    implicitReleaseAfter (or URLLC-Timer) ENUMERATED {e2, e3, e4, e8,e16, e32, e64, e128, e256, e512},     p0-URLLC SEQUENCE {     p0-NominalPUSCH-URLLC INTEGER (−126..24),      p0-UE-PUSCH-URLLCINTEGER (−8..7)     }  OPTIONAL, -- Need OP N1PUCCH-AN-PersistentList::= SEQUENCE (SIZE (1..4)) OF INTEGER (0..2047) -- ASN1STOP

To better serve the UL URLLC, some modifications or enhancements may beapplied to the URLLC-SPS. A URLLC-specific RNTI (e.g., URLLCSchedC-RNTIin Listing 2) may be used to differentiate the URLLC resource ortransmission from other services.

Additionally or alternatively, a period of URLLC-SPS (e.g.,URLLCInterval in Listing 2) may be short enough (e.g., slot1, slot2,slot4) to meet the latency requirement. In NR, time granularity may besubframe based, slot based, mini-slot based, and/or OFDM symbol (OS)based. (The term “OS” may be used to denote both OFDM symbols andDFT-Spread OFDM symbols as both of those will have been specified inNR.) In Listing 2, the slot may be given as an example. In general, thetime resource of URLLC-SPS may be determined by TTI index at startingtime, period, and/or TTI offset. All the parameters related to timedomain resource may be configured by RRC. Additionally or alternatively,parts of the parameters (e.g., period) may be configured by RRC andremaining parameters (e.g., TTI index/offset) may be indicated by DCIfor (re-) activation or dynamic scheduling. In a case that a mini-slotis used, the mini-slot location (mini-slot/OS index/offset, length,and/or bitmap) in a configured slot may be semi-statically configured inaddition to the slot-based time domain resource configuration. Themini-slot location information may be configured by RRC or indicated byDCI for (re-)activation and/or dynamic scheduling. In some approaches,the frequency resource of the URLLC-SPS may be configured by RRC orindicated by DCI for (re-)activation or dynamic scheduling.

Additionally or alternatively, the number of UL URLLC repetitions (e.g.,numberOfRepetition in Listing 2, also referred as repetition number) maybe semi-statically configured for URLLC-SPS. The repetition number maybe configured by RRC or indicated by DCI for (re-)activation or dynamicscheduling. Or, the set of repetition numbers may be configured by RRCand the choice of repetition number may be indicated by DCI for(re-)activation or dynamic scheduling.

Additionally or alternatively, the number of HARQ processes (e.g.,numberOfConfURLLC-Processes in Listing 2) may be configured forURLLC-SPS. The HARQ Process ID (also referred as HARQ Process Number,HPN) of a URLLC UL transmission at the configured URLLC resource may bedetermined by the TTI index, number of repetitions, and/or number ofHARQ processes. For example, the HARQ Process ID associated with thisTTI may be derived from the following equation: HARQ ProcessID=floor{[floor(CURRENT_TTI/URLLCInterval)]/numberOfRepetition} modulonumberOfConfURLLC-Processes, where CURRENT_TTI is the TTI index. Thenumber of HARQ processes may not be used if URLLC-SPS is aligned withsynchronous UL HARQ. In some approaches, only one HARQ process is usedfor URLLC-SPS. The number of HARQ processes may not be used. On theother hand, a specific HARQ Process ID may be allocated to thisURLLC-SPS.

Additionally or alternatively, a timer (e.g., implicitReleaseAfter (orURLLC-Timer) in Listing 2) may be configured for URLLC-SPS. The timermay start from the activation of URLLC-SPS, the first transmission afterthe activation, an empty (or silent) transmission after a URLLC-SPStransmission, or a URLLC-SPS transmission followed by an empty (silent)transmission. After a number (the value is given byimplicitReleaseAfter) of empty (or silent) transmissions counted fromthe start of the timer (in other words, the timer expires) at theconfigured URLLC-SPS resource, the URLLC-SPS may be deactivatedimplicitly.

In some approaches, in addition to a configured grant-free resource, thegNB/eNB 160 (e.g., gNB URLLC module 194) may send DCI indicating aDynamic Scheduling resource (also referred to as DS resource orgrant-based resource, for example). Here, the DS resource may include(e.g., correspond to) an UL resource, a frequency resource, UL-SCHresource, and/or PUSCH resource. The DS resource may use a differentresource compared to a configured resource for UL URLLC transmission(s).Alternatively, the DS resource may override the configured resource forUL URLLC transmission(s). Alternatively, the DS resource may use thesame resource as the configured resource for UL URLLC transmission(s).Alternatively, the DS resource may be preempted by grant-freetransmission (e.g., puncturing, superposition). A time/frequencyresource may be included in the DCI format.

Accordingly, a UE 102 with URLLC capability may support an SPS resource,URLLC-SPS resource and/or DS resource. The SPS resource and/or URLLC-SPSresource may be used for grant-free transmission. The DS resource may beused for grant-based transmission. A UE 102 may be configured withmultiple SPS resources or multiple URLLC-SPS resources (e.g., multipleperiodicities and/or multiple TTI offsets). The SPS resource and/or DSresource may be used by either the URLLC service or other services likeeMBB. The URLLC-SPS resource may be URLLC-specific withenhancements/modifications. In a specification, there may be only onekind of grant-free resource, which may be a combination of the SPSresource and/or the URLLC-SPS resource.

To differentiate service types, different Radio Network TemporaryIdentifiers (RNTIs) may be allocated to a URLLC UE 102. For example, aCell RNTI (C-RNTI) may be used for dynamic scheduled unicasttransmission. A SPS C-RNTI may be used for semi-persistent scheduledunicast transmission (activation, reactivation, retransmission, and/ordeactivation). For URLLC, the UE 102 may reuse the C-RNTI and/or the SPSC-RNTI, which means that no specific C-RNTI may be issued for URLLC. Inanother approach, a URLLC-specific identification referred to as a URLLCC-RNTI (a specification may use a different name, and URLLC C-RNTI isused as an example) may be used for URLLC related transmission. A URLLCC-RNTI may be used for dynamic scheduled transmission. Additionally oralternatively, the URLLC C-RNTI may be used for a semi-persistentscheduled URLLC transmission (activation, reactivation, retransmission,and/or deactivation). Additionally or alternatively, the URLLC C-RNTImay be used for dynamic reconfiguration of an UL grant-free URLLCtransmission.

A URLLC UE 102 may monitor several search spaces: common search space,UE-specific search space, and/or URLLC search space. The common searchspace may contain some information related to URLLC. There may be noURLLC-specific search space, or URLLC may share the same UE-specificsearch space with other services. To obtain URLLC related information,the UE 102 may search the UE-specific search space by using URLLC C-RNTI(if implemented and/or utilized, for example) or C-RNTI/SPS C-RNTI (ifthere is no URLLC-specific RNTI, for example). URLLC may have a specificsearch space, which may be referred to as a URLLC search space as anexample (a specification may use a different name). The UE 102 mayobtain URLLC related information by searching the URLLC search space.

To differentiate whether a transmission is an initial transmission or aretransmission, some mechanisms may be implemented and/or utilized insome approaches. For a grant-based transmission, additional bit(s) inDCI may be used to indicate whether the transmission is new data or not.Alternatively, some field(s) in DCI may be set as default value(s) toindicate whether the transmission is new data or not. For grant-freetransmission, each transmission at the configured grant-free resourcemay be only for initial transmission. If repetitions are supported, theUE 102 may repeat a TB for a predefined number of times and then repeattransmissions of new TB. In another approach, a time window may be used.Within the time window, the transmissions may be for the same TB. Afterthe time window expires, the grant-free transmission may be for a newTB.

Any physical layer resource may be used by grant-free transmission orgrant-based transmission, URLLC service or other services like eMBB,initial transmission or retransmission. In some approaches, each kind oftransmission may use a corresponding specific dedicated resource toavoid conflict. In some approaches, different transmissions may sharethe same resource for efficiency. For example, a configured grant-freeresource may be overridden, pre-empted, or punctured by a grant-basedtransmission or may not be used by a grant-based transmission. Theconfigured URLLC resource may be only for URLLC transmission, or may beshared by other services.

The UE operations module 124 may provide information 148 to the one ormore receivers 120. For example, the UE operations module 124 may informthe receiver(s) 120 when to receive retransmissions.

The UE operations module 124 may provide information 138 to thedemodulator 114. For example, the UE operations module 124 may informthe demodulator 114 of a modulation pattern anticipated fortransmissions from the gNB 160.

The UE operations module 124 may provide information 136 to the decoder108. For example, the UE operations module 124 may inform the decoder108 of an anticipated encoding for transmissions from the gNB 160.

The UE operations module 124 may provide information 142 to the encoder150. The information 142 may include data to be encoded and/orinstructions for encoding. For example, the UE operations module 124 mayinstruct the encoder 150 to encode transmission data 146 and/or otherinformation 142. The other information 142 may include PDSCH HARQ-ACKinformation.

The encoder 150 may encode transmission data 146 and/or otherinformation 142 provided by the UE operations module 124. For example,encoding the data 146 and/or other information 142 may involve errordetection and/or correction coding, mapping data to space, time and/orfrequency resources for transmission, multiplexing, etc. The encoder 150may provide encoded data 152 to the modulator 154.

The UE operations module 124 may provide information 144 to themodulator 154. For example, the UE operations module 124 may inform themodulator 154 of a modulation type (e.g., constellation mapping) to beused for transmissions to the gNB 160. The modulator 154 may modulatethe encoded data 152 to provide one or more modulated signals 156 to theone or more transmitters 158.

The UE operations module 124 may provide information 140 to the one ormore transmitters 158. This information 140 may include instructions forthe one or more transmitters 158. For example, the UE operations module124 may instruct the one or more transmitters 158 when to transmit asignal to the gNB 160. For instance, the one or more transmitters 158may transmit during a UL subframe. The one or more transmitters 158 mayupconvert and transmit the modulated signal(s) 156 to one or more gNBs160.

Each of the one or more gNBs 160 may include one or more transceivers176, one or more demodulators 172, one or more decoders 166, one or moreencoders 109, one or more modulators 113, a data buffer 162 and a gNBoperations module 182. For example, one or more reception and/ortransmission paths may be implemented in a gNB 160. For convenience,only a single transceiver 176, decoder 166, demodulator 172, encoder 109and modulator 113 are illustrated in the gNB 160, though multipleparallel elements (e.g., transceivers 176, decoders 166, demodulators172, encoders 109 and modulators 113) may be implemented.

The transceiver 176 may include one or more receivers 178 and one ormore transmitters 117. The one or more receivers 178 may receive signalsfrom the UE 102 using one or more antennas 180 a-n. For example, thereceiver 178 may receive and downconvert signals to produce one or morereceived signals 174. The one or more received signals 174 may beprovided to a demodulator 172. The one or more transmitters 117 maytransmit signals to the UE 102 using one or more antennas 180 a-n. Forexample, the one or more transmitters 117 may upconvert and transmit oneor more modulated signals 115.

The demodulator 172 may demodulate the one or more received signals 174to produce one or more demodulated signals 170. The one or moredemodulated signals 170 may be provided to the decoder 166. The gNB 160may use the decoder 166 to decode signals. The decoder 166 may produceone or more decoded signals 164, 168. For example, a first eNB-decodedsignal 164 may comprise received payload data, which may be stored in adata buffer 162. A second eNB-decoded signal 168 may comprise overheaddata and/or control data. For example, the second eNB-decoded signal 168may provide data (e.g., PDSCH HARQ-ACK information) that may be used bythe gNB operations module 182 to perform one or more operations.

In general, the gNB operations module 182 may enable the gNB 160 tocommunicate with the one or more UEs 102. The gNB operations module 182may include a gNB URLLC module 194. The gNB URLLC module 194 may performURLLC operations as described herein.

The gNB operations module 182 may provide information 188 to thedemodulator 172. For example, the gNB operations module 182 may informthe demodulator 172 of a modulation pattern anticipated fortransmissions from the UE(s) 102.

The gNB operations module 182 may provide information 186 to the decoder166. For example, the gNB operations module 182 may inform the decoder166 of an anticipated encoding for transmissions from the UE(s) 102.

The gNB operations module 182 may provide information 101 to the encoder109. The information 101 may include data to be encoded and/orinstructions for encoding. For example, the gNB operations module 182may instruct the encoder 109 to encode information 101, includingtransmission data 105.

The encoder 109 may encode transmission data 105 and/or otherinformation included in the information 101 provided by the gNBoperations module 182. For example, encoding the data 105 and/or otherinformation included in the information 101 may involve error detectionand/or correction coding, mapping data to space, time and/or frequencyresources for transmission, multiplexing, etc. The encoder 109 mayprovide encoded data 111 to the modulator 113. The transmission data 105may include network data to be relayed to the UE 102.

The gNB operations module 182 may provide information 103 to themodulator 113. This information 103 may include instructions for themodulator 113. For example, the gNB operations module 182 may inform themodulator 113 of a modulation type (e.g., constellation mapping) to beused for transmissions to the UE(s) 102. The modulator 113 may modulatethe encoded data 111 to provide one or more modulated signals 115 to theone or more transmitters 117.

The gNB operations module 182 may provide information 192 to the one ormore transmitters 117. This information 192 may include instructions forthe one or more transmitters 117. For example, the gNB operations module182 may instruct the one or more transmitters 117 when to (or when notto) transmit a signal to the UE(s) 102. The one or more transmitters 117may upconvert and transmit the modulated signal(s) 115 to one or moreUEs 102.

It should be noted that a DL subframe may be transmitted from the gNB160 to one or more UEs 102 and that a UL subframe may be transmittedfrom one or more UEs 102 to the gNB 160. Furthermore, both the gNB 160and the one or more UEs 102 may transmit data in a standard specialsubframe.

It should also be noted that one or more of the elements or partsthereof included in the eNB(s) 160 and UE(s) 102 may be implemented inhardware. For example, one or more of these elements or parts thereofmay be implemented as a chip, circuitry or hardware components, etc. Itshould also be noted that one or more of the functions or methodsdescribed herein may be implemented in and/or performed using hardware.For example, one or more of the methods described herein may beimplemented in and/or realized using a chipset, an application-specificintegrated circuit (ASIC), a large-scale integrated circuit (LSI) orintegrated circuit, etc.

URLLC may coexist with other services (e.g., eMBB). Due to the latencyrequirement, URLLC may have a highest priority in some approaches. Someexamples of URLLC coexistence with other services are given herein(e.g., in one or more of the following Figure descriptions).

FIG. 2 is diagram illustrating some examples of grant-based URLLC andgrant-based eMBB. For grant-based URLLC and grant-based eMBB, if a timedelay between UL grant reception in DL and UL data (PUSCH) transmissionis the same for both services, the coexistence issue may be solved bygNB/eNB scheduling. The UL grant for URLLC and UL grant for eMBB mayindicate different frequency resources (e.g., different resource blocks)or different time resources (e.g., different mini-slots/OFDM symbolswithin the slot/subframe). Additionally or alternatively, rate matchingor puncturing may be used for eMBB to protect URLLC data. Additionallyor alternatively, a gNB/eNB 160 may not send UL grant for eMBB to a UE102 if the gNB/eNB 160 sends an UL grant for URLLC to that UE 102 (or adifferent UE) at the same timing, so that possible resourceoverlapping/conflict can be avoided. FIG. 2 illustrates some examples.

FIG. 3 is a diagram illustrating some examples of grant-based URLLC andgrant-based eMBB. If a time delay between UL grant reception in DL andUL data transmission is shorter for URLLC due to the latencyrequirement, a resource may already be allocated by an earlier UL grantfor the eMBB service when a gNB/eNB 160 sends an UL grant for URLLCservice, which may use the same resource or part(s) of the sameresource. In some cases, a gNB/eNB 160 may send the UL grant to indicatea different resource (e.g., a different frequency resource and/or adifferent time resource) for URLLC. In some cases, a gNB/eNB 160 maysend the UL grant for URLLC to preempt (e.g., puncture and/or superpose)the resource that is already granted for eMBB. Since both services aregrant-based, no extra indication may be needed for decoding at thegNB/eNB 160. Some examples are shown in FIG. 3.

FIG. 4 is a diagram illustrating examples of grant-free URLLC andgrant-based eMBB. For grant-free URLLC and grant-based eMBB, agrant-free URLLC resource may be pre-configured. When a UE 102 has URLLCdata, the UE 102 may transmit at the configured resource. Thegrant-based eMBB may avoid the configured grant-free URLLC resource,which means that the configured resource may be dedicated for URLLC.However, a URLLC UE 102 may skip the configured resource if there is noURLLC data. In another approach, to enhance the resource utilizationefficiency, grant-based eMBB may be allowed to use a configured URLLCresource. If a configured URLLC resource is granted for eMBB but the UE102 has URLLC data to transmit at the configured resource, the URLLCdata may preempt the eMBB service or the UE 102 may abandon the eMBBtransmission. An indication may indicate the presence of URLLC data tohelp the gNB/eNB 160 decode, or the gNB/eNB 160 may assume there isURLLC data at the configured resource and blind decode the URLLC datafirst. Some examples are shown in FIG. 4. The indication may indicatewhich codeblock in a group of codeblocks comprising a transport blockwas affected by URLLC transmission; if multiple codeblocks in atransport block were affected by URLLC transmission there would bemultiple indications transmitted per transport block.

For grant-free URLLC and grant-free eMBB, a URLLC resource and an eMBBresource can be orthogonal to each other by configuration. However, ifoverlapping exists, the URLLC resource may override the eMBB resource.

FIG. 5 is a diagram illustrating examples of grant-based URLLC andgrant-free eMBB. For grant-based URLLC and grant-free eMBB, grant-basedURLLC may override grant-free eMBB. Some examples are shown in FIG. 5.

For URLLC itself, some mechanisms may be utilized to handlegrant-free/grant-based transmissions coexistence and initialtransmission/retransmission coexistence. Some examples are given inconnection with one or more of the following Figures.

FIG. 6 is a diagram illustrating examples of grant-based initialtransmission and grant-free initial transmission. For grant-basedinitial transmission and grant-free initial transmission, grant-basedinitial transmission may override grant-free initial transmission. Someexamples are shown in FIG. 6.

FIGS. 7A-7B are diagrams illustrating examples of grant-basedretransmission and grant-free initial transmission. For grant-basedretransmission and grant-free initial transmission, grant-basedretransmission may avoid configuring a grant-free resource. Grant-basedretransmission may override grant-free initial transmission. In adifferent design, grant-free initial transmission may overridegrant-based retransmission. Some examples are shown in FIGS. 7A-7B. Itshould be noted that in some approaches, an initial “repetition” may bean initial transmission. For example, “Rep 0” or a zeroth “repetition”may not be a repeat of an earlier transmission, but may be an initialtransmission, while “Rep 1” may be a repeat of an earlier transmission(e.g., a retransmission of Rep 0, which may or may not use a differentRV or MCS).

FIG. 8 is a diagram illustrating examples of grant-free initialtransmission and grant-free retransmission. For grant-free initialtransmission and grant-free retransmission, grant-free retransmissionmay override grant-free initial transmission. In a different approach,grant-free initial transmission may override grant-free retransmission.Some examples are shown in FIG. 8.

FIG. 9 is a diagram illustrating examples of grant-based retransmissionand grant-free retransmission. For grant-based retransmission andgrant-free retransmission, grant-based retransmission may overridegrant-free retransmission. Some examples are shown in FIG. 9.

FIG. 10 is a diagram illustrating examples of synchronous HARQ andasynchronous HARQ. NR may support synchronous HARQ, asynchronous HARQ orcombination/enhancement of synchronous HARQ and asynchronous HARQ for ULtransmission. For synchronous HARQ, timing between two adjacenttransmissions in a HARQ process may be fixed. A HARQ process ID may bederived from the TTI (subframe/slot/mini-slot/OS) index. Forasynchronous HARQ, timing between two adjacent transmissions in a HARQprocess may be dynamic. A HARQ process ID may be explicitly indicated.Some examples of synchronous HARQ and synchronous HARQ are shown in FIG.10.

Different services may use different types of HARQ procedures. Differenttypes of transmissions may use different types of HARQ procedures. Forexample, a URLLC service may use synchronous HARQ, while an eMBB servicemay use asynchronous HARQ. Additionally or alternatively, an initialtransmission may use synchronous HARQ, while retransmission may useasynchronous HARQ.

FIGS. 11A-11B are diagrams illustrating examples of mini-slots. In someimplementations, one or more mini-slots may be used in NR. Mini-slottransmission may use the same HARQ timing and procedure as regular HARQ(e.g., slot/subframe-based HARQ) or use a separate HARQ design. A UE 102may support only one mini-slot in a slot in some approaches. In thiscase, mini-slot HARQ can align with slot-based HARQ. A UE 102 maysupport multiple mini-slots in a slot in some approaches, where thesemini-slots may be used for repetitions of a same TB. In this case,mini-slot transmissions in a same slot may belong to a same HARQ processso that mini-slot HARQ can still align with slot-based HARQ. A UE 102may have multiple mini-slots in a slot and each mini-slot may use itsown HARQ process in some approaches. In this case, for synchronous HARQ,a HARQ process ID may be associated with the slot index and mini-slotoffset. For asynchronous HARQ, a HARQ process ID may be indicated by ULgrant. Some examples are shown in FIGS. 11A-11B.

FIG. 12 is a diagram illustrating examples of HARQ procedures. In someapproaches, URLLC may share HARQ processes with other services. In thiscase, each HARQ process may be used by URLLC or other services. In someapproaches, URLLC may use separate HARQ processes. In this case, a URLLCservice may be differentiated from other services by a correspondingdedicated HARQ process or a dedicated HARQ process ID. Some examples ofURLLC-specific HARQ process for synchronous HARQ and asynchronous HARQare shown separately in FIG. 12.

FIG. 13 is a diagram illustrating examples of repetitions. Repetitionsmay be a set of transmissions for a same TB. Repetitions of a same TBmay belong to a same HARQ process. To address the coexistence of arepetition HARQ process and a regular HARQ process, some mechanisms maybe utilized and/or implemented. Repetitions of a same TB may only useTTIs that are corresponding to the same HARQ process in the case ofsynchronous HARQ. HARQ process ID of repetitions may be determined bythe HARQ process ID of the first transmission. Repetitions may useconfigured resources and dedicated HARQ process(es). Some examples areshown in FIG. 13.

FIG. 14 is a diagram illustrating examples of grant-free transmission.For grant-free transmission, an UL grant may not be used so that HARQprocess ID may not be indicated by DCI explicitly. A HARQ process ID ofa grant-free transmission may be derived from a corresponding TTI indexor the TTI index of a corresponding first repetition. However,grant-based retransmission can be either synchronous or asynchronous. Byindicating HARQ process ID in the UL grant, for instance, a UE 102 mayknow which TB should be transmitted. Some examples are shown in FIG. 14.

FIGS. 15A-15B are diagrams illustrating examples of multiple HARQprocesses. For a single UE 102, multiple HARQ process may be supportedin a single TTI in some approaches. For example, in a single TTI, a UE102 may have a HARQ process for URLLC and a HARQ process for eMBB. Someexamples are shown in FIGS. 15A-15B.

There may be different modes to handling activation, deactivation,reactivation, adjustment, modification, ACK/NACK, repetitions, and/orterminations (i.e., the terminations of the PUSCH transmission(s) (e.g.,K repetitions), the stopping of the PUSCH transmission(s) (e.g., Krepetitions)). For example, for the UE configured with the grant-free ULtransmission (which may be referred as the UL transmission without thegrant), there may be different modes to handling,activation/deactivation, reactivation/adjustment/modification, ACK/NACK,repetitions, terminations and so on.

For example, the UE may start (initiate) the PUSCH transmission(s) basedon the activation (i.e., after the activation) as described above. Also,the UE may start the PUSCH transmission(s) based on the RRCconfiguration (i.e., after the RRC parameters are configured). The gNBmay configure the PUSCH transmission with the activation or the withoutthe activation. Namely, based on the configuration (e.g., the higherlayer configuration), the UE may change (switch) a behavior for thePUSCH initial transmission. For example, in a case that the PUSCHtransmission with the activation (e.g., the PUSCH transmission after theactivation) is configured, the UE may perform the PUSCH initialtransmission based on the activation being received. Also, in a casethat the PUSCH transmission without the activation is configured, the UEmay perform the PUSCH initial transmission based on the RRCconfiguration being received.

For example, a parameter skipActivation may be specified (specificationmay use a different name) in the RRC signaling (i.e., the RRC message).And, if the parameter skipActivation is set as false (or notconfigured), the UE may not perform the PUSCH initial transmission untilthe PUSCH transmission is activated. Namely, the UE may not perform thePUSCH transmission until grant-free transmission is activated. This modeis denoted as activation mode A for short. Namely, the activation mode Amay include a mode for the UE to perform the PUSCH transmission afterthe activation. And, if the parameter skipActivation is set as true (orconfigured), the UE may perform the PUSCH initial transmission (withoutthe activation) based on the RRC configuration being received. Namely,the UE may perform the PUSCH transmission without the activation if allthe related parameters are already configured by the higher layer. Thismode is denoted as activation mode B for short. Namely, the activationmode B may include a mode for the UE to perform the PUSCH transmissionwithout the activation (based on the RRC configuration).

Also, the UE may adjust or modify some parameters for the ULtransmission (i.e., the PUSCH transmission) without the grant. Theadjustment or modification may be done (indicated and/or configured) byLayer 1 (Physical Layer, L1) signaling or the higher layer signaling(e.g., the RRC signaling and/or the MAC CE), which may depend on thehigher layer configuration. For example, a parameter L1modification maybe specified (specification may use a different name) in the RRCsignaling. If the parameter L1modification is set as false (or notconfigured), the UE may not adjust or modify any parameters for the ULtransmission without the grant until the higher layer signaling (e.g.,the RRC and/or the MAC CE) for adjustment/modification of parameters isreceived (i.e., the higher layer parameters are received). This mode isdenoted as a modification mode A for short. Namely, the modificationmode A may include a mode for the UE to use the RRC parameters (i.e.,the higher layer parameters) for the PUSCH transmission(s). Also, if theparameter L1modification is set as true (or configured), the UE mayreceive signaling on the PDCCH (e.g., the DCI, the L1 signaling) toadjust/modify the parameters for the UL transmission without the grant.Namely, the UE may use the PDCCH (e.g., the DCI, the L1 signaling) toadjust/modify the parameters. In this case, the UE may need to sendHARQ-ACK (i.e., ACK/NACK feedback) for this PDCCH (i.e., the DCI, the L1signaling) reception. Here, the PDCCH may be scrambled by the C-RNTI,the SPS C-RNTI and/or the URLLC C-RNTI, etc., which will be describedbelow. Also, the UE may monitor the PDCCH in (on) the cell-specificsearch space (the CSS) or the UE-specific search space (the USS). Thismode is denoted as a modification mode B for short. Namely, themodification mode B may include a mode for the UE to use the PDCCH(i.e., the DCI, the L1 signaling) for the PUSCH transmission(s).

Here, the gNB may transmit, to the UE, HARQ-ACK (i.e., a positiveacknowledgment (ACK) and/or a negative acknowledgment (NACK)) for thePUSCH transmission(s) (e.g., the UL transmission without the grant).Namely, the UE may receive, from the gNB, the HARQ-ACK for PUSCHtransmission(s). For example, a separate channel, which may be similarto Physical Hybrid-ARQ Indicator Channel (PHICH), may be used for theHARQ-ACK feedback from gNB. This mode is denoted by an acknowledgementmode A. Namely, the acknowledgment mode A may include a mode for the UEto receive the HARQ-ACK on a physical downlink channel other than thePDCCH.

In yet another example, the HARQ-ACK feedback may be included in(transmitted by using) a common DCI (a common PDCCH and/or acell-specific UL grant). Here, the UE may detect the common DCI in theCSS (e.g., a cell-specific search space). Here, the HARQ-ACK feedback(s)may be bundled for multiple UEs. Namely, the single common DCI may beused for the transmission of the HARQ-ACK feedback to multiple UEs. Forexample, some fields (e.g., a first field) of the common DCI may be usedfor indicating the HARQ-ACK (i.e., ACK/NACK information). Also, the UEIDs (e.g., an index of the UE IDs, an index of the C-RNTI and/or the SPSC-RNTI assigned by the gNB) may be included in the corresponding fields(e.g., a second field, a second field which corresponds to the firstfield) explicitly or implicitly. This mode is denoted by anacknowledgement mode B. For example, the acknowledgment mode B mayinclude a mode for the UE to receive the HARQ-ACK by using the commonDCI (e.g., the common PDCCH, e.g., in the CSS).

In yet another example, the HARQ-ACK (e.g., ACK/NACK feedback) may beincluded in (transmitted by using) a UE-specific DCI (a UE-specificPDCCH and/or a UE-specific UL grant). Here, the UE may detect theUE-specific DCI in the USS. This mode is denoted by an acknowledgementmode C. For example, the acknowledgment mode C may include a mode forthe UE to receive the HARQ-ACK by using the UE-specific DCI (e.g., theUE-specific PDCCH, e.g., in the USS).

In yet another example, the HARQ-ACK (e.g., ACK/NACK feedback) may notbe needed explicitly. Namely, for example, only the UL grant (i.e., theUL grant itself) may be used for indicating a new transmission (i.e.,the initial transmission) and/or the retransmission. For example, aparameter AckTimer may be specified (specification may use a differentname) in the RRC signaling. Namely, if the parameter AckTimer isconfigured, the UE may flush the buffer in a case that no UL grant forthe same TB is not received within AckTimer TTIs (e.g., subframes,slots, mini-slots, OFDM symbols) after the corresponding ULtransmission. This mode is denoted by an acknowledgement mode D forshort. Namely, the acknowledgment mode D may include a mode for the UEto use the parameter AckTimer for the PUSCH transmission.

In the examples above, only ACK may be necessary for indicating theHARQ-ACK feedback. Namely, the gNB may indicate, to the UE(s), only ACKfor the PUSCH transmission. Here, the retransmission of the PUSCHtransmission (e.g., the retransmission for the same TB) may be indicatedby using the UL grant, which also serves the negative acknowledgement(NACK) (i.e., the UL grant, which may be used for indicating the NACK).

Besides the HARQ-ACK feedback (e.g., ACK/NACK may or may not be used),the UL grant may be used for indicating the UL transmission without thegrant (e.g., the PUSCH transmission). For example, while the UE performsthe PUSCH transmission(s) (e.g., the PUSCH transmission(s) without thegrant), the UE may also receive the UL grant used for indicating the newtransmission and/or the retransmission. Here, how to handle the UL grantfor the UL transmission without the grant may depend on the higher layerconfiguration or be determined by some parts of the specifications. Forexample, a parameter AckULgrant may be specified (specification may usea different name) in the RRC signaling. And, if the parameter AckULgrantis configured by using the RRC signaling (or if the parameter AckULgrantis specified by specification), the UE may always assume (consider,interpret, treat) the UL grant as ACK for the PUSCH transmission (e.g.,a previous transmission, a corresponding PUSCH transmission). This modeis denoted by an UL grant mode A for short. Namely, the UL grant mode Amay include a mode for the UE to always assume the UL grant as ACK forthe PUSCH transmission. Namely, the UL grant mode A may include a modefor the UE to stop (not perform) the PUSCH (re)transmission (and/or therepetition of the PUSCH transmission(s)) in a case that the UL grant isdetected (received). Namely, the UL grant mode A may include a mode forthe UE to stop (not perform) the PUSCH (re)transmission (and/or therepetition of the PUSCH transmission(s)) based on the detection of theUL grant (e.g., the DCI included in the UL grant). Namely, the mode Amay include a mode for the UE to terminate the PUSCH (re)transmission(and/or the repetition of the PUSCH transmission(s)) based on thedetection of the UL grant. Here, the details of the UL grant aredescribed below.

In yet another example, a parameter NackULgrant may be specified(specification may use a different name) in the RRC signaling. And, ifthe parameter NackULgrant is configured by using RRC signaling (or theparameter AckULgrant is not configured by using the RRC signaling, or ifthe parameter NackULgrant is specified by specification), the UE mayalways assume (consider, interpret, treat) the UL grant as NACK for thePUSCH transmission (e.g., a previous transmission, a corresponding PUSCHtransmission). This mode is denoted by an UL grant mode B for short.Namely, the UL grant mode B may include a mode for the UE to alwaysassume the UL grant as NACK for the PUSCH transmission. Namely, the ULgrant mode B may include a mode for the UE to perform the PUSCH(re)transmission (and/or the repetition of the PUSCH transmission(s)) ina case that the UL grant is detected (received). Namely, the UL grantmode B may include a mode for the UE to perform the PUSCH(re)transmission (and/or the repetition of the PUSCH transmission(s))based on the detection of the UL grant (e.g., the DCI included in the ULgrant). Namely, the mode B may include a mode for the UE to notterminate the PUSCH (re)transmission (and/or the repetition of the PUSCHtransmission(s)) based on the detection of the UL grant. Here, thedetails of the UL grant are described below.

Additionally and/or alternatively, if the parameter NackULgrant isconfigured by using RRC signaling (or the parameter AckULgrant is notconfigured by using the RRC signaling, or if the parameter NackULgrantis specified by specification), the UE may always assume (consider,interpret, treat) the UL grant as ACK and/or NACK for the PUSCHtransmission (e.g., a previous transmission, a corresponding PUSCHtransmission). Namely, information (e.g., a new data indicator, a HARQprocess ID) included in the UL grant may be used for indicating ACK forthe PUSCH transmission (i.e., indicating the new transmission) and/orNACK for the PUSCH transmission (i.e., indicating the retransmission).Namely, a value(s) set to an information field(s) included in the ULgrant may be used for indicating the initial transmission and/or theretransmission. This mode is also denoted by UL grant mode B for short.

Namely, the UL grant mode B may include a mode for the UE to assume theUL grant as ACK and/or NACK for the PUSCH transmission. Namely, the ULgrant mode B may include a mode for the UE to perform the PUSCH(re)transmission (and/or the repetition of the PUSCH transmission(s)) ina case that the UL grant indicating the retransmission (i.e., the DCIincluded in the UL grant indicating the retransmission (e.g., NACK)) isdetected (received). Also, the UL grant mode B may include a mode forthe UE to stop (not perform) the PUSCH (re)transmission (and/or therepetition of the PUSCH transmission(s)) in a case that the UL grantindicating the initial transmission (i.e., the DCI included in the ULgrant indicating the initial transmission (e.g., ACK)) is detected(received). Here, the UE may perform the PUSCH initial transmission in acase the UL grant indicating the initial transmission is detected.

Namely, the UL grant mode B may include a mode for the UE to perform thePUSCH (re)transmission (and/or the repetition of the PUSCHtransmission(s)) based on the detection of the DCI (included in the ULgrant) indicating the retransmission. Also, the UL grant mode B mayinclude a mode for the UE to stop (not perform) the PUSCH(re)transmission (and/or the repetition of the PUSCH transmission(s))based on the detection of the DCI (included in the UL grant) indicatingthe initial transmission. Namely, the mode B may include a mode for theUE to not terminate the PUSCH (re)transmission (and/or the repetition ofthe PUSCH transmission(s)) based on the detection of the DCI (includedin the UL grant) indicating the retransmission. Also, the mode B mayinclude a mode for the UE to terminate the PUSCH (re)transmission(and/or the repetition of the PUSCH transmission(s)) based on thedetection of the DCI (included in the UL grant) indicating the initialtransmission. Namely, the mode B may include a mode for the UE toperform the PUSCH initial transmission (and/or the initial transmissionof the repetition of the PUSCH transmission(s)) based on the detectionof the DCI (included in the UL grant) indicating the initialtransmission. Here, the details of the UL grant are described below.

Also, the repetitions (i.e., the repetitions of the PUSCHtransmission(s)) may or may not be supported for the PUSCH transmission(e.g., the UL transmission without the grant). For example, a parameterrepetition-Config may be specified (specification may use a differentname) in the RRC signaling. And, if the parameter repetition-Config isset as true (or configured) by using the RRC signaling, the UE mayperform the K repetitions including the initial transmission for thesame transport block (e.g., the K may be defined, in advance, by thespecification, or the K may be configured (or indicated) by using theRRC signaling (or by using the DCI (e.g., the PDCCH))). Also, if theparameter repetition-Config is set as false (or not configured), the UEmay not perform the repetitions of the PUSCH transmission (i.e., the UEmay not use the repetitions of the PUSCH transmission, the UE mayperform the single PUSCH transmission). In yet another example, aparameter numberOfRepetition (i.e. the number of the K) may be specifiedin the higher layer. And, if the parameter numberOfRepetition is set to“1” by using the higher layer (e.g. the RRC signaling, MAC CE), the UEmay not perform the repetitions of the PUSCH transmission. Also, if theparameter numberOfRepetition is set to a value greater than 1, the UEmay perform the K repetitions (e.g., including the initial transmissionfor the same transport block). In yet another example, a set of K valuesmay be configured by the RRC signaling and the selection of K (i.e., asingle value of K among a set of K values) for the UL transmissionwithout the grant is indicated by L1 signaling (i.e., the DCI, thePDCCH) or the MAC CE.

For the repetitions of the PUSCH transmission (i.e., the ULrepetitions), as described above, the termination of repetitions may beused (indicated) or not (not indicated). For example, a parameterNoearlytermination may be specified (specification may use a differentname) in the RRC signaling. And, if the parameter Noearlytermination isconfigured by using the RRC signaling (or if the parameterNoearlytermination is specified by specification), the UE may notterminate the repetitions of the PUSCH transmission until the number ofrepetitions for that TB reaches K. In yet another example, a parameterearlyACK may be specified (specification may use a different name) inthe RRC signaling. And, if a parameter earlyACK is configured by usingthe RRC signaling (or if a parameter earlyACK is specified byspecification), the UE may terminate the repetitions when ACK isreceived (e.g., ACK is received even though the number of repetitionsfor that TB may not reach K). Here, as described above, ACK may betransmitted on the physical downlink channel. Also, ACK may betransmitted by using the common DCI. Also, ACK may be transmitted byusing the UE-specific DCI. In yet another example, a parameterearlyULgrant may be specified (specification may use a different name)in the RRC signaling. And, if the parameter earlyULgrant is configuredby using the RRC signaling (or if the parameter earlyULgrant isspecified by specification), the UE may terminate the repetitions in acase that the UL grant is received. Namely, the UE may terminate therepetitions based on the detection of the UL grant (e.g., even thoughthe number of repetitions for that TB may not reach K).

On the other hand, besides UE-specific RNTIs, UE may have (be assignedby the gNB) one or more kinds of common Radio Network TemporaryIdentifiers (RNTIs). One example is Paging RNTI (P-RNTI), which is usedfor Paging Message. Another example is System Information RNTI(SI-RNTI), which is used for transmission of SIB messages. Yet anotherexample is Random Access RNTI (RA-RNTI) which is used for PRACHResponse. Yet another example is Temporary C-RNTI (T-RNTI), which isused during RACH.

If parameters used for the PUSCH transmission (e.g., the UL transmissionwithout the grant), such as a time resource(s) (e.g. a periodicityand/or a offset value (e.g., TTI offset)), a frequency resource(s) (e.g.an index of Physical Resource Block (PRB)), a spatial resource(s) (e.g.,an antenna port, the number of the antenna port for the ULtransmission), MCS, the repetition number K and/or the hopping pattern,are configured by using the RRC signaling, the UE may perform, based onthe configured parameters, the PUSCH transmission (the UL datatransmission) without L1 signaling (i.e., without the activation). Here,as described above, in a case that the UE is configured to skip theactivation (e.g., the parameter skipActivation is configured by usingthe RRC signaling or it is determined by some parts of thespecification), the UE may perform the PUSCH transmission using theconfigured parameters (e.g., the configured resource(s)) without L1signaling (i.e., without the activation). And, as described above, ifthe UE is configured with the L1modification for the parameters of theUL transmission without grant (e.g. the parameter L1modification isconfigured by using the RRC signaling or it is determined by some partsof the specification), the UE may monitor the PDCCH (the DCI, the ULgrant) to check whether the related parameters will be modified. Namely,only in a case that the parameter L1modification is configured, the UEmay monitor the PDCCH (the DCI, the UL grant) used for modifying theparameters.

Here, if a specific C-RNTI (e.g., the C-RNTI, the SPS C-RNTI, and/or theURLLC C-RNTI) is assigned for the PUSCH transmission (e.g., the ULtransmission without the grant) (i.e., the UL transmission based on theparameters configured by using RRC signaling) and the specific RNTI isdenoted by C-RNTI 1, the PDCCH (the DCI, the UL grant) used forparameters modification may be scrambled by the C-RNTI 1. To indicatethat the PDCCH (the DCI, the UL grant) is used for parametersmodification, some fields may be set as defaulted values, e.g., TPCfield in the DCI may be set as all 0, or cyclic shirt DMRS field may beset as all 0. Namely, in a case that each of one or more fields includedin the DCI (e.g., the PDCCH) may be set to each of certain values, theDCI (e.g., the PDCCH) may be used for modifying the parameters. Here,one or more fields and/or the certain values may be defined, in advance,by the specification and known information between the gNB and the UE.Also, to change (e.g., modify) some parameters (e.g., a value(s) of aparameter(s)) for the PUSCH transmission (e.g., the UL transmissionwithout the grant), the corresponding fields (these fields may usedifferent names in specifications) in the DCI, such as the MCS, therepetition number (if there is), the hopping pattern (if there is), theindex of PRB, etc., may be adjusted. In some cases, the DCI format maynot include the corresponding fields for the parameter adjustment. Somefields may be reused for the parameter adjustment. For example, theremay not be the repetition number field (or the hopping pattern field).For example, as described above, the set of the repetition numbers maybe configured by using the RRC signaling and one of the set of therepetition numbers may be indicated by using the DCI (e.g., the PDCCH).Here, for example, in a case that the PDCCH is used for the changing(e.g., modifying) the parameter(s) (e.g., the value(s) of theparameter(s)), a value of TPC command for PUCCH (i.e., a value set to afield of the TPC command for PUCCH) may be used for indicating theparameter(s) (e.g., the value(s) of the parameter(s)). Also, forexample, in a case that the PDCCH is used for the changing (e.g.,modifying) the parameter(s) (e.g., the value(s) of the parameter(s)), avalue of HARQ process number (i.e., a value set to a field of the HARQprocess number) may be used for indicating the parameter(s) (e.g., thevalue(s) of the parameter(s)). Some other fields may be used for themodification of the repetition number (or the hopping pattern), e.g.,the TPC field is reused for indicating the repetition number (or thehopping pattern):

TABLE 1 Value of ‘TPC command for PUCCH’ Repetition number K ‘00’Repetition number a ‘01’ Repetition number b ‘10’ Repetition number c‘11’ Repetition number dor

TABLE 2 Value of ‘TPC command for PUCCH’ Hopping pattern ‘00’ Hoppingpattern a ‘01’ Hopping pattern b ‘10’ Hopping pattern c ‘11’ Hoppingpattern dOr, HARQ process number field (if present) is reused to indicationrepetition number (or hopping pattern):

TABLE 3 Value of ‘HARQ process number’ Repetition number K ‘000’Repetition number a ‘001’ Repetition number b ‘010’ Repetition number c‘011’ Repetition number d ‘100’ Repetition number e ‘101’ Repetitionnumber f ‘110’ Repetition number g ‘111’ Repetition number hOr

TABLE 4 Value of ‘HARQ process number’ Hopping pattern ‘000’ Hoppingpattern a ‘001’ Hopping pattern b ‘010’ Hopping pattern c ‘011’ Hoppingpattern d ‘100’ Hopping pattern e ‘101’ Hopping pattern f ‘110’ Hoppingpattern g ‘111’ Hopping pattern h

For example, the UE may use the following procedure to modify theparameters for the PUSCH transmission (e.g., the UL transmission withoutthe grant). Namely, as a Step 1, the UE may monitor PDCCH (e.g., thePDCCH scrambled by a specific C-RNTI assigned to this UL transmissionwithout grant, the PDCCH with the specific C-RNTI). And, as a Step 2,the UE may verify the PDCCH (the DCI, the UL grant) by checking thepredefined field(s) (as described above). And, if the predefinedfield(s) are set to the predefined values, as a Step 3, the UE maymodify the parameters for the PUSCH transmission (e.g., the ULtransmission without the grant) based on the values of the relatedfield(s). And, as a Step 4, the UE may transmit the HARQ-ACK (e.g.,ACK/NACK feedback) to indicate whether the parameters modification issuccessful or not. Namely, the UE may transmit the HARQ-ACK for the DCI(e.g., the PDCCH) used for modifying the parameters. For example, the UEmay transmit, on the PUCCH, the HARQ-ACK for the DCI (e.g., the PDCCH)used for modifying the parameters. Also, for example, the UE maytransmit, by using the MAC CE, the HARQ-ACK for the DCI (e.g., thePDCCH) used for modifying the parameters. As an example, the UE maymonitor the PDCCH (e.g., the PDCCH scrambled by the C-RNTI 1, the PDCCHwith the C-RNTI 1). If the TPC field in the DCI is set as all 0 and thecyclic shirt for DMRS field is set as all 0, the UE may modify the MCSand the frequency resource for the PUSCH transmission (e.g., the ULtransmission without the grant) based on the value(s) of MCS field andPRB field in the DCI and adjusts the repetition number based on the HARQprocess number field by looking up Table 3. Finally, the UE send anacknowledgement to the UE indicating the L1modification is successful.

Here, if the UE may not be configured to the skip activation (e.g., ifthe parameter skipActivation is not configured by using the RRCsignaling or some parts of the specification determined that activationis required), the UE may perform the PUSCH transmission after the DCIindicating the activation is received (i.e., the UE may transmit UL dataat the configured resource after L1 activation). Here, some parametersused for the PUSCH transmission (e.g., the UL transmission without thegrant), such as the time resource(s) (e.g. the periodicity and/or theoffset value (e.g., the TTI offset)), the spatial resource (e.g., theantenna port, the number of the antenna port), the set of the repetitionnumbers and/or the set of the hopping pattern, may be configured byusing the RRC signaling. Also, some parameters (e.g., some otherparameters) may be included in the DCI indicating the activation (i.e.,the PDCCH, the L1 activation), such as the frequency resource(s) (e.g.the index of PRB), the MCS, the repetition number K and/or the hoppingpattern. Also, the specific C-RNTI (e.g., the SPS C-RNTI, and/or theURLLC C-RNTI) may be assigned for the PUSCH transmission (e.g., the ULtransmission without the grant) by using the RRC signaling, and thespecific RNTI is also denoted by the C-RNTI 1 here (it may be or may notnecessarily be a same C-RNTI as the UL transmission configured with theskipping activation above), the PDCCH (the DCI, the UL grant) used forthe activation (i.e., the L1 activation) may be scrambled by the C-RNTI1 (i.e., the PDCCH with the C-RNTI 1). The design of the PDCCH (the DCI,the UL grant) used for the activation (i.e., the L1 activation) may besimilar to the PDCCH (the DCI, the UL grant) used for the parametersmodification described above. To indicate that the PDCCH (the DCI, theUL grant) is used for activation/reactivation, some fields may be set toa defaulted value(s), e.g., the TPC field in the DCI may be set as all0, or the cyclic shirt for DMRS field may be set as all 0. To set orreset some parameters for the PUSCH transmission (e.g., the ULtransmission without the grant), the corresponding fields (these fieldsmay use different names in specifications) in the DCI, such as the MCS,the repetition number (if there is), the hopping pattern (if there is),the PRB index, etc., may be adjusted. In some cases, the DCI format maynot include the corresponding fields for the parameter setup oradjustment. Some fields may be reused for the parameter setup oradjustment. For example, there may not be the repetition number field(or the hopping pattern field). Some other fields may be used for themodification of the repetition number (or the hopping pattern), e.g.,the TPC field or the HARQ process number field may be reused forindicating the repetition number (or the hopping pattern) like Table1-4. The procedure is a little bit different. In general, as a Step 1,some related parameters may be configured for the PUSCH transmission(e.g., the UL transmission without the grant) by using the RRCsignaling; as a Step 2, the UE may monitor the PDCCH scrambled by thespecific C-RNTI (e.g., the PDCCH with the specific C-RNTI assigned tothis UL transmission without the grant); as a Step 3, the UE may verifythe PDCCH (the DCI, the UL grant) by checking the predefined fields; ifthese fields are set to the predefined values, as a Step 4, the UE setremaining parameters for the PUSCH transmission (e.g., the ULtransmission without the grant) based on the values of the relatedfields; as a Step 5, the UE transmit the HARQ-ACK used for indicatingwhether the activation is successful or not; if the activation issuccessful, as a Step 6, the UE may start the PUSCH transmission (e.g.,the UL transmission without the grant) based on the parameters; and theUE may repeat Step 2-6 to reactivate or adjust the parameters for thePUSCH transmission (e.g., the UL transmission without the grant).

Here, the specific C-RNTI (e.g., the C-RNTI, the SPS C-RNTI, and/or theURLLC C-RNTI) may be assigned for the PUSCH transmission (e.g., the ULtransmission without the grant) by using the RRC signaling and thespecific RNTI is also denoted by the C-RNTI 1. The PDCCH (the DCI, theUL grant) scrambled by the C-RNTI 1 (i.e., the PDCCH with the C-RNTI)may be used not only for the activation, reactivation, parametersmodification, and/or adjustment but also ACK/NACK feedback or the ULgrant for (re)transmission. Here, if the parameter AckULgrant(specification may use a different name) is configured by using the RRCsignaling or it may be specified by specification, the UE may alwaysassume (consider, interpret, treat) the UL grant (with some fields setas default values) as ACK for the PUSCH transmission (e.g., a previoustransmission) in the indicated HARQ process and/or the UL grant mayindicate a new transmission. Without receiving the UL grant, the UE mayretransmit at the configured resource without the grant. A procedure isdescribed as example: after the PUSCH transmission (e.g., the ULtransmission without the grant), the UE may receive the corresponding ULgrant scrambled by RNTI 1 then UE may flush the buffer of the TB in theprevious transmission. If the parameter NackULgrant (specification mayuse a different name) is configured by using the RRC signaling or it maybe specified by specification, the UE may always assume (consider,interpret, treat) the UL grant as NACK for the PUSCH transmission (e.g.,a previous transmission) in the indicated HARQ process. The UL grant mayalso indicate a retransmission. A procedure is described as example:after the PUSCH transmission (e.g., the UL transmission without thegrant), the UE may receive the corresponding UL grant (for the same HARQprocess) scrambled by C-RNTI 1 then UE may retransmit by following theUL grant. If neither AckULgrant or NackULgrant is configured, someinformation (e.g. the new data indicator, and/or the HARQ process ID)included in the UL grant may be used for indicating whether it is apositive acknowledgment (ACK) or a negative acknowledgement (NACL) forthe previous transmission. A procedure is described as example: afterthe PUSCH transmission (e.g., the UL transmission without the grant),the UE may receive the corresponding UL grant (for the same HARQprocess) scrambled by C-RNTI 1. If the NDI (New Data Indicator field)indicates “0”, the UE transmits a new TB by following the UL grant. IfNDI indicates “1”, UE retransmits the same TB by following the UL grant.

The UE may have a group common C-RNTI, which is denoted by C-RNTI 2. TheUE may monitor the PDCCH (the DCI, the UL grant) scrambled by C-RNTI 2.The PDCCH (the DCI, the UL grant) scrambled by the C-RNTI 2 may be usedfor ACK feedback of the PUSCH transmission (e.g., the UL transmissionwithout the grant). Some fields in the DCI may contain information forUE identification. The general procedure may be as follows: as a Step 1,the UE may transmit, in a timing index n (e.g., in a subframe, in aslot, in a mini-slot, in a OFDM symbol); as a step 2, the UE may monitorthe corresponding PDCCH scrambled by C-RNTI 2 in a timing index n+D (Dmay be configured (indicated, determined) by using the RRC signaling orother parts of specification); as a Step 3, the UE checks the predefinedfields (e.g., the MCS field, the HARQ process number field, the TPCfield, the cyclic shirt for DMRS field, etc.) in the DCI and verify itsID information by predefined rules (e.g., the i-th bit in the predefinedfield indicates “1” and i is corresponding to the UE ID, or the value ofUE ID is explicit indicated in the predefined field.); if theverification is successful, as a Step 4, the UE may flush the buffer ofthe corresponding transmission.

The UE may have a UE-specific C-RNTI, which is obtained from the RACHprocedure. The UE-specific C-RNTI is denoted by C-RNTI 0 here. The UE(e.g., the UE configured with the grant-free transmission) may alsomonitor the PDCCH (the DCI, the UL grant) scrambled by C-RNTI 0. The UEmay not expect to receive the PDCCH (the DCI, the UL grant) scrambled byC-RNTI 0 for the same HARQ process(es) of the PUSCH transmission (e.g.,the UL transmission without the grant_. In yet a different design, theUE may receive the PDCCH (the DCI, the UL grant) scrambled by the C-RNTI0 for the same HARQ process(es) of the PUSCH transmission (e.g., the ULtransmission without the grant). In this case, the UE may always assumethat the UL grant is for the new transmission (or the retransmission).

Here, as described above, the UE may monitor a set of candidates of theDL control channel(s) (e.g., the PDCCH). Also, the set of candidates ofthe DL control channel(s) which the UE monitors may be also referred toas the search space (e.g., the CSS and/or the USS). And, the RNTI(s)assigned to the UE may be used for transmission of DCI (transmission ofDL control channel(s)). For example, the UE may attempt to decode DCI towhich the CRC parity bits scrambled by the RNTI(s) are attached, anddetects the DL control channel (e.g., the PCCH (e.g., the PDCCH), theDCI, the DCI format). That is, the UE may decode the DL controlchannel(s) with the CRC scrambled by the RNTI(s). That is, the UE maymonitor the DL control channel(s) with the RNTI(s). Namely, for example,the UE may monitor the UL grant with the RNTI(s).

Here, as described above, the RNTI(s) may include, at least, the C-RNTI(Cell-RNTI), the SPS C-RNTI, the RA-RNTI (Random Access-RNTI) and/or theTemporary C-RNTI. For example, the C-RNTI may be a unique identificationused for identifying RRC connection and scheduling. Here, the PDCCH(e.g., the DCI) with the C-RNTI may be detected (received) in the CSSand/or the USS. Also, the SPS C-RNTI may be a unique identification usedfor semi-persistent scheduling. Here, the PDCCH (e.g., the DCI) with theSPS C-RNTI may be detected (received) in the CSS and/or the USS. Also,the RA-RNTI may be an identification used for the random-accessprocedure. Here, the PDCCH (e.g., the DCI) with the RA-RNTI may bedetected in the CSS (i.e., the CSS only). Also, the Temporary C-RNTI maybe used for the random-access procedure. Here, the Temporary C-RNTI maybe detected in the CSS (i.e., the CSS only)/

Also, a random-access procedure may be performed between the gNB and theUE. For example, the random-access procedure may include a contentionbased random access procedure and a non-contention based random accessprocedure. For instance, the contention based random access proceduremay be a 4-step procedure which includes a message 1 (Msg.1), a message2 (Msg.2), a message 3 (Msg.3), and a message 4 (Msg.4).

For example, the UE may transmit the random-access preamble (i.e., theMsg.1) based on a random-access channel configuration (i.e., RACHconfiguration). And, the gNB may transmit the random-access response(i.e., the Msg.2) which corresponds to the random-access preambletransmission (i.e., the Msg.1). And, the UE may perform a scheduled anUL-SCH transmission (i.e., the Msg.3) (i.e., the PUSCH transmission)based on the random-access response (i.e., the Msg.2). And, the gNB maytransmit the contention resolution (i.e., Msg.4) based on the scheduledUL-SCH transmission.

For example, in Random Access Resource selection (e.g., PRACHselection), the UE 602 may randomly select the random-access preambleand/or the random-access channel resource (i.e., the RACH resource).And, the UE may perform the random access preamble transmission (i.e.,the Msg. 1 transmission) using the selected random access preambleand/or the selected RACH resource. And, in the random access responsereception, the UE may receive the random access response (i.e., theMsg.2). For example, once the random access preamble is transmitted, theUE may monitor the PDCCH for the random access response(s) identified bythe RA-RNTI. Here, the PDCCH with the RA-RNTI monitored by the UE may beused for scheduling of the PDSCH on which the random access response isreceived (i.e., transmitted). Here, the PDCCH with the RA-RNTI may beused only for the contention based random access procedure.

The random-access response may be received on the DL-SCH (i.e., thePDSCH). And, the random-access response (e.g., the MAC RAR (MAC RandomAccess Response(s))) may include the random-access response grant whichis used for scheduling of the PUSCH for the Msg. 3 transmission. Here,the random-access response grant may be used only for the contentionbased random access procedure. Also, the random-access response mayinclude a timing advance command for the PUSCH transmission (i.e., theMsg. 3 transmission). Also, the random-access response may include theTemporary C-RNTI. The Temporary C-RNTI may be used for indication aretransmission of the PUSCH transmission (i.e., the Msg.3).

Also, in the scheduled PUSCH transmission, the UE may perform a timingadjustment for the PUSCH transmission based on the timing advancecommand. And, the UE may perform the PUSCH transmission (i.e., the Msg.3 transmission) based on the random-access response grant. Here, thePUSCH transmission may include an identity used for identifying the UE(Initial UE-Identity of the C-RNTI). Namely, the gNB may identify the UEafter receiving the PUSCH transmission (i.e., the Msg. 3 transmission).Also, the UE perform a retransmission (e.g., an adaptive retransmission)of the Msg.3 in a case that the Msg. 3 retransmission is indicated byusing the PDCCH with the Temporary C-RNTI. Namely, the UE may performthe PUSCH transmission (i.e., the Msg. 3 transmission) which correspondsto a random-access response grant in the contention based random accessprocedure. Also, the UE may perform the PUSCH transmission (i.e., theMsg. 3 transmission) which corresponds to a retransmission (e.g., aretransmission of the same transport block) in the contention basedrandom access procedure.

Also, in Contention Resolution, in a case that a contention resolutionidentity which is received from the gNB is matched to the InitialUE-Identity, the UE 602 may consider the contention resolutionsuccessful. Also, in a case that the PDCCH with the C-RNTI is received,the UE may consider the contention resolution successful. Then, the UEmay consider the random-access procedure successfully completed.

Here, as described above, the UE performs the PUSCH transmission(s)based on the detection of the UL grant (i.e., the PDCCH). For example,the UE may perform the PUSCH transmission(s) based on the detection ofthe UL grant with the C-RNTI (i.e., the UL grant to which the CRC paritybits scrambled by the C-RNTI are attached). For example, the UL grantwith the C-RNTI (e.g., the DCI included in the UL grant with the C-RNTI)may be used for indicating the initial transmission and/or theretransmission. Also, the UE may perform the PUSCH transmission(s) basedon the detection of the UL grant with the SPS C-RNTI. Here, the UL grantwith the SPS C-RNTI (e.g., the DCI included in the UL grant with the SPSC-RNTI) may be used for activating, deactivating, and/or modifying thePUSCH transmission(s) (i.e., the SPS scheduling, the SPS resource).Also, the UL grant with the SPS C-RNTI may be used for indicating theinitial transmission and/or the retransmission.

Also, the UE may perform the PUSCH transmission(s) based on thedetection of the UL grant with the URLLC C-RNTI. Here, the UL grant withthe URLLC C-RNTI (e.g., the DCI included in the UL grant with the URLLCC-RNTI) may be used for activating, deactivating, and/or modifying thePUSCH transmission(s) (i.e., the SPS scheduling, the SPS resource).Also, the UL grant with the URLLC C-RNTI may be used for indicating theinitial transmission and/or the retransmission. Also, the UE may performthe PUSCH transmission(s) based on the detection of the common DCI(i.e., the UL grant). As described above, the common DCI may be used forindicating the HARQ-ACK (i.e., the positive acknowledgment (i.e., ACK)or the negative acknowledgment (i.e., NACK)). Here, the common DCI maybe used for indicating the initial transmission and/or theretransmission.

Also, as described above, the UE may perform the PUSCH transmission(i.e., the Msg. 3 transmission) based on the random-access responsegrant (i.e., the UL grant). The random-access repose grant may beincluded in the random-access response (e.g., the MAC RAR) that isscheduled by using the PDCCH with the RA-RNTI (the DCI format with theRA-RNTI). For example, the random-access response grant may be used forindication the initial transmission. Also, the UE may perform the PUSCHtransmission (i.e., the Msg. 3 transmission) based on the UL grant withthe Temporary C-RNTI.

Here, the UL grant with the C-RNTI, the UL grant with the SPS C-RNTI,the UL grant with the URLLC C-RNTI, and/or the common DCI may be assumedto be included in a first UL grant in some implementations for the sakeof simple description. Namely, the first UL grant may include the ULgrant with the C-RNTI. Also, the first UL grant may include the UL grantwith the SPS C-RNTI. Also, the first UL grant may include the UL grantwith the URLLC C-RNTI. Also, the first UL grant may include the commonDCI.

Also, the UL grant with the C-RNTI, the UL grant with the SPS C-RNTI,the UL grant with the URLLC C-RNTI, the common DCI, the random-accessresponse grant, and/or the UL grant with the Temporary C-RNTI may beassumed to be included in a second UL grant in some implementations forthe sake of simple description. Namely, the second UL grant may includethe UL grant with the C-RNTI. Also, the second UL grant may include theUL grant with the SPS C-RNTI. Also, the second UL grant may include theUL grant with the URLLC C-RNTI. Also, the second UL grant may includethe common DCI. Also, the second UL grant may include the random-accessresponse grant. Also, the second UL grant may include the UL grant withthe Temporary C-RNTI.

Namely, each of the first UL grant and the second UL grant may beidentified by different RNTIs. Also, each of the first UL grant and thesecond UL grant may be identified by different size of information bits(different number of information bits). Also, each of the first UL grantand the second UL grant may be identified by the search space (i.e., theCSS, the USS) in which the UL grants (i.e., the first UL grant, thesecond UL grant) is detected. Also, each of the first UL grant and thesecond grant may be identified by utilization of the UL grants. Forexample, the first UL grant may be used for the dynamic and/or thesemi-persistent scheduled unicast transmission. Also, for example, thesecond UL grant may be used for the contention based random accessprocedure.

As described above, the gNB may transmit the parameter (e.g.,AckULgrant, and/or the NACKULgrant) used for configuring the UL grantmode(s) (e.g., the UL grant mode A, and/or the UL grant mode B). Here,for example, in a case that the UL grant mode A (i.e., the parameterAckULgrant) is configured, the UE may assume (consider, interpret,treat) the first UL grant as ACK. Namely, the UE (e.g., the UEconfigured with the UL grant mode A) may always assume (consider,interpret, treat) the first UL grant as the ACK based on the detectionof the first UL grant (e.g., the DCI included in the first UL grant).Namely, the UE (e.g., the UE configured with the UL grant mode A) maystop (e.g., not perform) the PUSCH transmission (e.g., the PUSCHretransmission) based on the detection of the first UL grant (e.g., theDCI included in the first UL grant). Here, in a case that the first ULgrant for the initial transmission is received (e.g., in a case that theDCI (included in the first UL grant) indicating the initial transmissionis received), the UE may perform the PUSCH transmission (e.g., the PUSCHinitial transmission). Namely, only in a case that the first UL grantfor the retransmission is received (e.g., only in a case that the DCI(included in the first UL grant) indicating the retransmission), the UEmay stop (e.g., not perform) the PUSCH transmission (e.g., the PUSCHretransmission) based on the detection of the first UL grant (e.g., theDCI included in the first UL grant).

Also, for example, in a case that the UL grant mode A (i.e., theparameter ACKgrant) is configured, the UE may assume (consider,interpret, treat) the second UL grant as the ACK and/or the NACK.Namely, the UE (e.g., the UE configured with the UL grant mode A) mayassume (consider, interpret, treat) the second UL grant as the ACKand/or the NACK based on the detection of the second UL grant (e.g., theDCI included in the second UL grant). Namely, the UE may stop (e.g., notperform) the PUSCH transmission (e.g., the PUSCH retransmission) in acase that the second UL grant (e.g., the DCI included in the second ULgrant) indicates no retransmission (i.e., in a case that the ACK isindicated by using the second UL grant, the initial transmission). Forexample, the UE may stop (e.g., not perform) the PUSCH transmission(e.g., the PUSCH retransmission) in a case that the second UL grant(e.g., the DCI included in the second UL grant) indicates the initialtransmission. Also, the UE may not stop (i.e., perform) the PUSCHtransmission (e.g., the PUSCH retransmission) in a case that the secondUL grant (e.g., the DCI included in the second UL grant) indicates theretransmission. Here, in a case that the second UL grant for the initialtransmission is received (e.g., in a case that the DCI (included in thesecond UL grant) indicating the initial transmission is received), theUE may perform the PUSCH transmission (e.g., the PUSCH initialtransmission) based on the detection of the second UL grant (e.g., theDCI included in the second UL grant). Namely, only in a case that thesecond UL grant for the retransmission is received (e.g., only in a casethat the DCI (included in the second UL grant) indicating theretransmission), the UE may stop (e.g., not perform) the PUSCHtransmission (e.g., the PUSCH retransmission). Also, only in a case thatthe second UL grant for the retransmission is received (e.g., only in acase that the DCI (included in the second UL grant) indicating theretransmission), the UE may perform the PUSCH transmission (e.g., thePUSCH retransmission).

Namely, the UE (e.g., the UE configured with the UL grant mode A) maychange (switch) a behavior for the PUSCH transmission (e.g., the PUSCHinitial transmission and/or the PUSCH retransmission) based on thedetected (received) UL grant. For example, the UE (e.g., the UEconfigured with the UL grant mode A) may change the behavior for thePUSCH transmission based on whether the detected UL grant is the firstUL grant or the second UL grant. Also, for example, the UE (e.g., the UEconfigured with the UL grant mode A) may change the behavior for thePUSCH transmission (e.g., the PUSCH initial transmission and/or thePUSCH retransmission) based on whether the search space in which the ULgrant is detected is the CSS or the USS. Also, the UE (e.g., the UEconfigured with the UL grant mode A) may stop the PUSCH transmission(e.g., the PUSCH retransmission) in a case that the second UL grant(e.g., the DCI included in the second UL grant) indicates no PUSCHretransmission (e.g., the initial transmission)). Also, the UE (e.g.,the UE configured with the UL grant mode A) may perform the PUSCHtransmission (e.g., the PUSCH retransmission) in a case that the secondUL grant (e.g., the DCI included in the second UL grant) indicates theretransmission.

For example, the UE (e.g., the UE configured with the UL grant mode A)may always stop the PUSCH transmission (e.g., the PUSCH retransmission)based on the detection of the UL grant with the C-RNTI (e.g., the DCIincluded in the UL grant with the C-RNTI). Also, the UE (e.g., the UEconfigured with the UL grant mode A) always stop the PUSCH transmission(e.g., the PUSCH retransmission) based on the detection of the UL grantwith the SPS C-RNTI (e.g., the DCI included in the UL grant with the SPSC-RNTI). Also, the UE (e.g., the UE configured with the UL grant mode A)always stop the PUSCH transmission (e.g., the PUSCH retransmission)based on the detection of the UL grant with the URLLC C-RNTI (e.g., theDCI included in the UL grant with the URLLC C-RNTI). Also, the UE (e.g.,the UE configured with the UL grant mode A) may not stop (i.e., perform)the PUSCH transmission (e.g., the PUSCH initial transmission) based onthe detection of the random-access response grant. Also, the UE (e.g.,the UE configured with the UL grant mode A) may not sop (i.e., perform)the PUSCH transmission (e.g., the PUSCH retransmission) based on thedetection of the UL grant with the Temporary C-RNTI.

Namely, the UE (the UE configured with the UL grant mode A) may stop thePUSCH transmission (e.g., the PUSCH retransmission) based on thedetection of the UL grant (i.e., the first UL grant) unless the PUSCHtransmission corresponds to the random access response grant (i.e., thesecond UL grant) in the contention based random access procedure or thePUSCH transmission corresponds to the retransmission of the sametransport block (i.e., the PUSCH transmission correspond to the UL grantwith the Temporary C-RNTI (i.e., the second UL grant)) in the contentionbased random access procedure. Also, the UE (the UE configured with theUL grant mode A) may not stop (i.e., perform) the PUSCH transmission(e.g., the PUSCH initial transmission and/or the PUSCH retransmission)based on the detection of the UL grant (i.e., the second UL grant) in acase that the PUSCH transmission corresponds to the random accessresponse grant (i.e., the second UL grant) in the contention basedrandom access procedure and/or the PUSCH transmission corresponds to theretransmission of the same transport block (i.e., the PUSCH transmissioncorrespond to the UL grant with the Temporary C-RNTI (i.e., the secondUL grant)) in the contention based random access procedure.

Here, the behavior of the UE configured with the UL grant mode B isdescribed above. Namely, for example, in a case that the UL grant mode B(i.e., the parameter NackULgrant) is configured, the UE may assume(consider, interpret, treat) the first UL grant as ACK and/or NACK.Namely, the UE (e.g., the UE configured with the UL grant mode B) mayassume (consider, interpret, treat) the first UL grant based on thedetection of the first UL grant (e.g., the DCI included in the first ULgrant). Namely, the UE may stop (e.g., not perform) the PUSCHtransmission (e.g., the PUSCH retransmission) in a case that the firstUL grant (e.g., the DCI included in the first UL grant) indicates noretransmission (i.e., in a case that the ACK is indicated by using thesecond UL grant, the initial transmission). Also, the UE may not stop(i.e., perform) the PUSCH transmission (e.g., the PUSCH retransmission)in a case that the first UL grant (e.g., the DCI included in the secondUL grant) indicates no retransmission (i.e., in a case that the ACK isindicated by using the first UL grant, the initial transmission). Here,in a case that the first UL grant for the initial transmission isreceived (e.g., in a case that the DCI (included in the first UL grant)indicating the initial transmission is received), the UE may perform thePUSCH transmission (e.g., the PUSCH initial transmission). Namely, onlyin a case that the first UL grant for the retransmission is received(e.g., only in a case that the DCI (included in the first UL grant)indicating the retransmission), the UE may stop (e.g., not perform) thePUSCH transmission (e.g., the PUSCH retransmission) in a case that thefirst UL grant (e.g., the DCI included in the first UL grant) indicatesno retransmission (i.e., the initial transmission). Also, only in a casethat the first UL grant for the retransmission is received (e.g., onlyin a case that the DCI (included in the first UL grant) indicating theretransmission), the UE may not stop (i.e., perform) the PUSCHtransmission (e.g., the PUSCH retransmission) in a case that the firstUL grant (e.g., the DCI included in the first UL grant) indicates theretransmission.

Also, for example, in a case that the UL grant mode B (i.e., theparameter Nackgrant) is configured, the UE may assume (consider,interpret, treat) the second UL grant as the ACK and/or the NACK.Namely, the UE (e.g., the UE configured with the UL grant mode B) mayassume (consider, interpret, treat) the second UL grant as the ACKand/or the NACK based on the detection of the second UL grant (e.g., theDCI included in the second UL grant). Namely, the UE may stop (e.g., notperform) the PUSCH transmission (e.g., the PUSCH retransmission) in acase that the second UL grant (e.g., the DCI included in the second ULgrant) indicates no PUSCH retransmission (i.e., in a case that the ACKis indicated by using the second UL grant, the initial transmission).For example, the UE may stop (e.g., not perform) the PUSCH transmission(e.g., the PUSCH retransmission) in a case that the second UL grant(e.g., the DCI included in the second UL grant) indicates noretransmission (e.g., the initial transmission). Also, the UE may notstop (e.g., perform) the PUSCH transmission (e.g., the PUSCHretransmission) in a case that the second UL grant (e.g., the DCIincluded in the second UL grant) indicates the retransmission. Here, ina case that the second UL grant for the initial transmission is received(e.g., in a case that the DCI (included in the second UL grant)indicating the initial transmission is received), the UE may perform thePUSCH transmission (e.g., the PUSCH initial transmission) based on thedetection of the second UL grant (e.g., the DCI included in the secondUL grant). Namely, only in a case that the second UL grant for theretransmission is received (e.g., only in a case that the DCI (includedin the second UL grant) indicating the retransmission), the UE may stop(e.g., not perform) the PUSCH transmission (e.g., the PUSCHretransmission). Also, only in a case that the second UL grant for theretransmission is received (e.g., only in a case that the DCI (includedin the second UL grant) indicating the retransmission), the UE mayperform the PUSCH transmission (e.g., the PUSCH retransmission).

Namely, the UE (e.g., the UE configured with the UL grant mode B) maynot change (switch) a behavior for the PUSCH transmission (e.g., thePUSCH initial transmission and/or the PUSCH retransmission) based on thedetected (received) UL grant (i.e., regardless of the detected(received) UL grant). For example, the UE (e.g., the UE configured withthe UL grant mode B) may not change the behavior for the PUSCHtransmission regardless of whether the detected UL grant is the first ULgrant or the second UL grant. Also, for example, the UE (e.g., the UEconfigured with the UL grant mode B) may not change the behavior for thePUSCH transmission (e.g., the PUSCH initial transmission and/or thePUSCH retransmission) regardless of whether the search space in whichthe UL grant is detected is the CSS or the USS. Namely, the UE (e.g.,the UE configured with the UL grant mode B) may always stop the PUSCHtransmission (e.g., the PUSCH retransmission) in a case that the ULgrant (i.e., the first UL grant and/or the second UL grant, e.g., theDCI included in the first UL grant, and/or the DCI included in thesecond UL grant) indicates no PUSCH retransmission (e.g., the initialtransmission)). Also, the UE (e.g., the UE configured with the UL grantmode A) may always perform the PUSCH transmission (e.g., the PUSCHretransmission) in a case that the UL grant (i.e., the first UL grantand/or the second UL grant, e.g., the DCI included in the first ULgrant, and/or the DCI included in the second UL grant) indicates theretransmission.

For example, the UE (e.g., the UE configured with the UL grant mode B)may always stop the PUSCH transmission (e.g., the PUSCH retransmission)based on the detection of the UL grant (i.e., the UL grant with theC-RNTI, the UL grant SPS C-RNTI, the UL grant with the URLLC C-RNTI, therandom-access response grant and/or the UL grant with the TemporaryC-RNTI). Also, the UE (e.g., the UE configured with the UL grant mode A)may not stop (i.e., perform) the PUSCH transmission (e.g., the PUSCHinitial transmission) based on the detection of the UL grant (i.e., theUL grant with the C-RNTI, the UL grant SPS C-RNTI, the UL grant with theURLLC C-RNTI, the random-access response grant and/or the UL grant withthe Temporary C-RNTI).

Namely, the UE (the UE configured with the UL grant mode B) may stop thePUSCH transmission (e.g., the PUSCH retransmission) based on thedetection of the UL grant (i.e., the first UL grant, and/or the secondUL grant) regardless of the PUSCH transmission corresponds to the randomaccess response grant (i.e., the second UL grant) in the contentionbased random access procedure or the PUSCH transmission corresponds tothe retransmission of the same transport block (i.e., the PUSCHtransmission correspond to the UL grant with the Temporary C-RNTI (i.e.,the second UL grant)) in the contention based random access procedure.

FIG. 16 is a diagram illustrating an example of a resource grid for thedownlink. The resource grid illustrated in FIG. 16 may be utilized insome implementations of the systems and methods disclosed herein. Moredetail regarding the resource grid is given in connection with FIG. 1.

In FIG. 16, one downlink subframe 1669 may include two downlink slots1683. N^(DL) _(RB) is downlink bandwidth configuration of the servingcell, expressed in multiples of N^(RB) _(sc), where N^(RB) _(sc) is aresource block 1689 size in the frequency domain expressed as a numberof subcarriers, and N^(DL) _(symb) is the number of OFDM symbols 1687 ina downlink slot 1683. A resource block 1689 may include a number ofresource elements (RE) 1691.

For a PCell, N^(DL) _(RB) is broadcast as a part of system information.For an SCell (including an LAA SCell), N^(DL) _(RB) is RB configured bya RRC message dedicated to a UE 102. For PDSCH mapping, the available RE1691 may be the RE 1691 whose index 1 fulfils 1≥1_(data,start) and/or1_(data,end)≥1 in a subframe.

In the downlink, the OFDM access scheme with cyclic prefix (CP) may beemployed, which may be also referred to as CP-OFDM. In the downlink,PDCCH, EPDCCH, PDSCH and the like may be transmitted. A downlink radioframe may include multiple pairs of downlink resource blocks (RBs) whichis also referred to as physical resource blocks (PRBs). The downlink RBpair is a unit for assigning downlink radio resources, defined by apredetermined bandwidth (RB bandwidth) and a time slot. The downlink RBpair includes two downlink RBs that are continuous in the time domain.

The downlink RB includes twelve sub-carriers in frequency domain andseven (for normal CP) or six (for extended CP) OFDM symbols in timedomain. A region defined by one sub-carrier in frequency domain and oneOFDM symbol in time domain is referred to as a resource element (RE) andis uniquely identified by the index pair (k,l) in a slot, where k and lare indices in the frequency and time domains, respectively. Whiledownlink subframes in one component carrier (CC) are discussed herein,downlink subframes are defined for each CC and downlink subframes aresubstantially in synchronization with each other among CCs.

FIG. 17 is a diagram illustrating one example of a resource grid for theuplink. The resource grid illustrated in FIG. 17 may be utilized in someimplementations of the systems and methods disclosed herein. More detailregarding the resource grid is given in connection with FIG. 1.

In FIG. 17, one uplink subframe 1769 may include two uplink slots 1783.N^(UL) _(RB) is uplink bandwidth configuration of the serving cell,expressed in multiples of N^(RB) _(sc), where N^(RB) _(sc) is a resourceblock 1789 size in the frequency domain expressed as a number ofsubcarriers, and N^(UL) _(symb) is the number of SC-FDMA symbols 1793 inan uplink slot 1783. A resource block 1789 may include a number ofresource elements (RE) 1791.

For a PCell, N^(UL) _(RB) is broadcast as a part of system information.For an SCell (including an LAA SCell), N^(UL) _(RB) is configured by aRRC message dedicated to a UE 102.

In the uplink, in addition to CP-OFDM, a Single-Carrier FrequencyDivision Multiple Access (SC-FDMA) access scheme may be employed, whichis also referred to as Discrete Fourier Transform-Spreading OFDM(DFT-S-OFDM). In the uplink, PUCCH, PUSCH, PRACH and the like may betransmitted. An uplink radio frame may include multiple pairs of uplinkresource blocks. The uplink RB pair is a unit for assigning uplink radioresources, defined by a predetermined bandwidth (RB bandwidth) and atime slot. The uplink RB pair includes two uplink RBs that arecontinuous in the time domain.

The uplink RB may include twelve sub-carriers in frequency domain andseven (for normal CP) or six (for extended CP) OFDM/DFT-S-OFDM symbolsin the time domain. A region defined by one sub-carrier in the frequencydomain and one OFDM/DFT-S-OFDM symbol in the time domain is referred toas a RE and is uniquely identified by the index pair (k,l) in a slot,where k and 1 are indices in the frequency and time domainsrespectively. While uplink subframes in one component carrier (CC) arediscussed herein, uplink subframes are defined for each CC.

FIG. 18 shows examples of several numerologies 1801. The numerology #11801 a may be a basic numerology (e.g., a reference numerology). Forexample, a RE 1895 a of the basic numerology 1801 a may be defined withsubcarrier spacing 1805 a of 15 kHz in frequency domain and 2048 Ts+CPlength (e.g., 160 Ts or 144 Ts) in time domain (i.e., symbol length #11803 a), where Ts denotes a baseband sampling time unit defined as1/(15000*2048) seconds. For the i-th numerology, the subcarrier spacing1805 may be equal to 15*2^(−i) and the effective OFDM symbol length2048*2^(−i)*Ts. It may cause the symbol length is 2048*2^(−i)*Ts+CPlength (e.g., 160*2^(−i)*Ts or 144*2^(−i)*Ts). In other words, thesubcarrier spacing of the i+1-th numerology is a double of the one forthe i-th numerology, and the symbol length of the i+1-th numerology is ahalf of the one for the i-th numerology. FIG. 18 shows fournumerologies, but the system may support another number of numerologies.Furthermore, the system does not have to support all of the 0-th to theI-th numerologies, i=0, 1, . . . , I.

For example, the first UL transmission on the first SPS resource asabove mentioned may be performed only on the numerology #1 (e.g., asubcarrier spacing of 15 kHz). Here, the UE 102 may acquire (detect) thenumerology #1 based on a synchronization signal. Also, the UE 102 mayreceive a dedicated RRC signal including information (e.g., a handovercommand) configuring the numerology #1. The dedicated RRC signal may bea UE-specific signal. Here, the first UL transmission on the first SPSresource may be performed on the numerology #1, the numerology #2 (asubcarrier spacing of 30 kHz), and/or the numerology #3 (a subcarrierspacing of 60 kHz).

Also, the second UL transmission on the second SPS resource as abovementioned may be performed only on the numerology #3. Here, for example,the UE 102 may receive System Information (e.g., Master InformationBlock (MIB) and/or System Information Block (SIB)) including informationconfiguring the numerology #2 and/or the numerology #3.

Also, the UE 102 may receive the dedicated RRC signal includinginformation (e.g., the handover command) configuring the numerology #2and/or the numerology #3. The System Information (e.g., MIB) may betransmitted on BCH (Broadcast Channel) and/or the dedicated RRC signal.The System Information (e.g., SIB) may contain information relevant whenevaluating if a UE 102 is allowed to access a cell and/or defines thescheduling of other system information. The System Information (SIB) maycontain radio resource configuration information that is common formultiple UEs 102. Namely, the dedicated RRC signal may include each ofmultiple numerology configurations (the first numerology, the secondnumerology, and/or the third numerology) for each of UL transmissions(e.g., each of UL-SCH transmissions, each of PUSCH transmissions). Also,the dedicated RRC signal may include each of multiple numerologyconfigurations (the first numerology, the second numerology, and/or thethird numerology) for each of DL transmissions (each of PDCCHtransmissions).

FIG. 19 shows examples of subframe structures for the numerologies 1901that are shown in FIG. 18. Given that a slot 283 includes N^(DL) _(symb)(or N^(UL) _(symb))=⁷ symbols, the slot length of the i+l-th numerology1901 is a half of the one for the i-th numerology 1901, and eventuallythe number of slots 283 in a subframe (i.e., 1 ms) becomes double. Itmay be noted that a radio frame may include 10 subframes, and the radioframe length may be equal to 10 ms.

FIG. 20 shows examples of slots 2083 and sub-slots 2007. If a sub-slot2007 is not configured by higher layer, the UE 102 and the eNB/gNB 160may only use a slot 2083 as a scheduling unit. More specifically, agiven transport block may be allocated to a slot 2083. If the sub-slot2007 is configured by higher layer, the UE 102 and the eNB/gNB 160 mayuse the sub-slot 2007 as well as the slot 2083. The sub-slot 2007 mayinclude one or more OFDM symbols. The maximum number of OFDM symbolsthat constitute the sub-slot 2007 may be N^(DL) _(symb)−1 (or N^(UL)_(symb)−1).

The sub-slot length may be configured by higher layer signaling.Alternatively, the sub-slot length may be indicated by a physical layercontrol channel (e.g., by DCI format).

The sub-slot 2007 may start at any symbol within a slot 2083 unless itcollides with a control channel. There could be restrictions ofmini-slot length based on restrictions on starting position. Forexample, the sub-slot 2007 with the length of N^(DL) _(symb)−1 (orN^(UL) _(symb)−1) may start at the second symbol in a slot 2083. Thestarting position of a sub-slot 2007 may be indicated by a physicallayer control channel (e.g., by DCI format). Alternatively, the startingposition of a sub-slot 2007 may be derived from information (e.g.,search space index, blind decoding candidate index, frequency and/ortime resource indices, Physical Resource Block (PRB) index, a controlchannel element index, control channel element aggregation level, anantenna port index, etc.) of the physical layer control channel whichschedules the data in the concerned sub-slot 2007.

In cases when the sub-slot 2007 is configured, a given transport blockmay be allocated to either a slot 2083, a sub-slot 2007, aggregatedsub-slots 2007 or aggregated sub-slot(s) 2007 and slot 2083. This unitmay also be a unit for HARQ-ACK bit generation.

FIG. 21 shows examples of scheduling timelines 2109. For a normal DLscheduling timeline 2109 a, DL control channels are mapped the initialpart of a slot 2183 a. The DL control channels 2111 schedule DL sharedchannels 2113 a in the same slot 2183 a. HARQ-ACKs for the DL sharedchannels 2113 a (i.e., HARQ-ACKs each of which indicates whether or nottransport block in each DL shared channel 2113 a is detectedsuccessfully) are reported via UL control channels 2115 a in a laterslot 2183 b. In this instance, a given slot 2183 may contain either oneof DL transmission and UL transmission.

For a normal UL scheduling timeline 2109 b, DL control channels 2111 bare mapped the initial part of a slot 2183 c. The DL control channels2111 b schedule UL shared channels 2117 a in a later slot 2183 d. Forthese cases, the association timing (time shift) between the DL slot2183 c and the UL slot 2183 d may be fixed or configured by higher layersignaling. Alternatively, it may be indicated by a physical layercontrol channel (e.g., the DL assignment DCI format, the UL grant DCIformat, or another DCI format such as UE-common signaling DCI formatwhich may be monitored in common search space).

For a self-contained base DL scheduling timeline 2109 c, DL controlchannels 2111 c are mapped to the initial part of a slot 2183 e. The DLcontrol channels 2111 c schedule DL shared channels 2113 b in the sameslot 2183 e. HARQ-ACKs for the DL shared channels 2113 b are reported inUL control channels 2115 b, which are mapped at the ending part of theslot 2183 e.

For a self-contained base UL scheduling timeline 2109 d, DL controlchannels 2111 d are mapped to the initial part of a slot 2183 f. The DLcontrol channels 2111 d schedule UL shared channels 2117 b in the sameslot 2183 f. For these cases, the slot 2183 f may contain DL and ULportions, and there may be a guard period between the DL and ULtransmissions.

The use of a self-contained slot may be upon a configuration ofself-contained slot. Alternatively, the use of a self-contained slot maybe upon a configuration of the sub-slot. Yet alternatively, the use of aself-contained slot may be upon a configuration of shortened physicalchannel (e.g., PDSCH, PUSCH, PUCCH, etc.).

FIG. 22 shows examples of DL control channel monitoring regions. One ormore sets of PRB(s) may be configured for DL control channel monitoring.In other words, a control resource set is, in the frequency domain, aset of PRBs within which the UE 102 attempts to blindly decode downlinkcontrol information, where the PRBs may or may not be frequencycontiguous, a UE 102 may have one or more control resource sets, and oneDCI message may be located within one control resource set. In thefrequency-domain, a PRB is the resource unit size (which may or may notinclude DMRS) for a control channel. A DL shared channel may start at alater OFDM symbol than the one(s) which carries the detected DL controlchannel. Alternatively, the DL shared channel may start at (or earlierthan) an OFDM symbol than the last OFDM symbol which carries thedetected DL control channel. In other words, dynamic reuse of at leastpart of resources in the control resource sets for data for the same ora different UE 102, at least in the frequency domain may be supported.

FIG. 23 shows examples of DL control channel which includes more thanone control channel elements. When the control resource set spansmultiple OFDM symbols, a control channel candidate may be mapped tomultiple OFDM symbols or may be mapped to a single OFDM symbol. One DLcontrol channel element may be mapped on REs defined by a single PRB anda single OFDM symbol. If more than one DL control channel elements areused for a single DL control channel transmission, DL control channelelement aggregation may be performed.

The number of aggregated DL control channel elements is referred to asDL control channel element aggregation level. The DL control channelelement aggregation level may be 1 or 2 to the power of an integer. ThegNB 160 may inform a UE 102 of which control channel candidates aremapped to each subset of OFDM symbols in the control resource set. Ifone DL control channel is mapped to a single OFDM symbol and does notspan multiple OFDM symbols, the DL control channel element aggregationis performed within an OFDM symbol, namely multiple DL control channelelements within an OFDM symbol are aggregated. Otherwise, DL controlchannel elements in different OFDM symbols can be aggregated.

FIG. 24 shows examples of UL control channel structures. UL controlchannel may be mapped on REs which may be defined based on a PRB and aslot in frequency and time domains, respectively. This UL controlchannel may be referred to as a long format (or just the 1st format). ULcontrol channels may be mapped on REs on a limited OFDM symbols in thetime domain. This may be referred to as a short format (or just the 2ndformat). The UL control channels with a short format may be mapped onREs within a single PRB. Alternatively, the UL control channels with ashort format may be mapped on REs within multiple PRBs. For example,interlaced mapping may be applied, namely the UL control channel may bemapped to every N PRBs (e.g., 5 or 10) within a system bandwidth.

FIG. 25 is a block diagram illustrating one implementation of a gNB2560. The gNB 2560 may include a higher layer processor 2523, a DLtransmitter 2525, a UL receiver 2533, and one or more antenna 2531. TheDL transmitter 2525 may include a PDCCH transmitter 2527 and a PDSCHtransmitter 2529. The UL receiver 2533 may include a PUCCH receiver 2535and a PUSCH receiver 2537.

The higher layer processor 2523 may manage physical layer's behaviors(the DL transmitter's and the UL receiver's behaviors) and providehigher layer parameters to the physical layer. The higher layerprocessor 2523 may obtain transport blocks from the physical layer. Thehigher layer processor 2523 may send/acquire higher layer messages suchas an RRC message and MAC message to/from a UE's higher layer. Thehigher layer processor 2523 may provide the PDSCH transmitter transportblocks and provide the PDCCH transmitter transmission parameters relatedto the transport blocks.

The DL transmitter 2525 may multiplex downlink physical channels anddownlink physical signals (including reservation signal) and transmitthem via transmission antennas 2531. The UL receiver 2533 may receivemultiplexed uplink physical channels and uplink physical signals viareceiving antennas 2531 and de-multiplex them. The PUCCH receiver 2535may provide the higher layer processor 2523 UCI. The PUSCH receiver 2537may provide the higher layer processor 2523 received transport blocks.

FIG. 26 is a block diagram illustrating one implementation of a UE 2602.The UE 2602 may include a higher layer processor 2623, a UL transmitter2651, a DL receiver 2643, and one or more antenna 2631. The ULtransmitter 2651 may include a PUCCH transmitter 2653 and a PUSCHtransmitter 2655. The DL receiver 2643 may include a PDCCH receiver 2645and a PDSCH receiver 2647.

The higher layer processor 2623 may manage physical layer's behaviors(the UL transmitter's and the DL receiver's behaviors) and providehigher layer parameters to the physical layer. The higher layerprocessor 2623 may obtain transport blocks from the physical layer. Thehigher layer processor 2623 may send/acquire higher layer messages suchas an RRC message and MAC message to/from a UE's higher layer. Thehigher layer processor 2623 may provide the PUSCH transmitter transportblocks and provide the PUCCH transmitter 2653 UCI.

The DL receiver 2643 may receive multiplexed downlink physical channelsand downlink physical signals via receiving antennas 2631 andde-multiplex them. The PDCCH receiver 2645 may provide the higher layerprocessor 2623 DCI. The PDSCH receiver 2647 may provide the higher layerprocessor 2623 received transport blocks.

It should be noted that names of physical channels described herein areexamples. The other names such as “NRPDCCH, NRPDSCH, NRPUCCH andNRPUSCH”, “new Generation-(G)PDCCH, GPDSCH, GPUCCH and GPUSCH” or thelike can be used.

FIG. 27 illustrates various components that may be utilized in a UE2702. The UE 2702 described in connection with FIG. 27 may beimplemented in accordance with the UE 102 described in connection withFIG. 1. The UE 2702 includes a processor 2703 that controls operation ofthe UE 2702. The processor 2703 may also be referred to as a centralprocessing unit (CPU). Memory 2705, which may include read-only memory(ROM), random access memory (RAM), a combination of the two or any typeof device that may store information, provides instructions 2707 a anddata 2709 a to the processor 2703. A portion of the memory 2705 may alsoinclude non-volatile random-access memory (NVRAM). Instructions 2707 band data 2709 b may also reside in the processor 2703. Instructions 2707b and/or data 2709 b loaded into the processor 2703 may also includeinstructions 2707 a and/or data 2709 a from memory 2705 that were loadedfor execution or processing by the processor 2703. The instructions 2707b may be executed by the processor 2703 to implement the methodsdescribed above.

The UE 2702 may also include a housing that contains one or moretransmitters 2758 and one or more receivers 2720 to allow transmissionand reception of data. The transmitter(s) 2758 and receiver(s) 2720 maybe combined into one or more transceivers 2718. One or more antennas2722 a-n are attached to the housing and electrically coupled to thetransceiver 2718.

The various components of the UE 2702 are coupled together by a bussystem 2711, which may include a power bus, a control signal bus and astatus signal bus, in addition to a data bus. However, for the sake ofclarity, the various buses are illustrated in FIG. 27 as the bus system2711. The UE 2702 may also include a digital signal processor (DSP) 2713for use in processing signals. The UE 2702 may also include acommunications interface 2715 that provides user access to the functionsof the UE 2702. The UE 2702 illustrated in FIG. 27 is a functional blockdiagram rather than a listing of specific components.

FIG. 28 illustrates various components that may be utilized in a gNB2860. The gNB 2860 described in connection with FIG. 28 may beimplemented in accordance with the gNB 280 described in connection withFIG. 1. The gNB 2860 includes a processor 2803 that controls operationof the gNB 2860. The processor 2803 may also be referred to as a centralprocessing unit (CPU). Memory 2805, which may include read-only memory(ROM), random access memory (RAM), a combination of the two or any typeof device that may store information, provides instructions 2807 a anddata 2809 a to the processor 2803. A portion of the memory 2805 may alsoinclude non-volatile random-access memory (NVRAM). Instructions 2807 band data 2809 b may also reside in the processor 2803. Instructions 2807b and/or data 2809 b loaded into the processor 2803 may also includeinstructions 2807 a and/or data 2809 a from memory 2805 that were loadedfor execution or processing by the processor 2803. The instructions 2807b may be executed by the processor 2803 to implement the methodsdescribed above.

The gNB 2860 may also include a housing that contains one or moretransmitters 2817 and one or more receivers 2878 to allow transmissionand reception of data. The transmitter(s) 2817 and receiver(s) 2878 maybe combined into one or more transceivers 2876. One or more antennas2880 a-n are attached to the housing and electrically coupled to thetransceiver 2876.

The various components of the gNB 2860 are coupled together by a bussystem 2811, which may include a power bus, a control signal bus and astatus signal bus, in addition to a data bus. However, for the sake ofclarity, the various buses are illustrated in FIG. 28 as the bus system2811. The gNB 2860 may also include a digital signal processor (DSP)2813 for use in processing signals. The gNB 2860 may also include acommunications interface 2815 that provides user access to the functionsof the gNB 2860. The gNB 2860 illustrated in FIG. 28 is a functionalblock diagram rather than a listing of specific components.

FIG. 29 is a block diagram illustrating one implementation of a UE 2902in which systems and methods for ultra-reliable and low-latencycommunication operations may be implemented. The UE 2902 includestransmit means 2958, receive means 2920 and control means 2924. Thetransmit means 2958, receive means 2920 and control means 2924 may beconfigured to perform one or more of the functions described inconnection with FIG. 1 above. FIG. 27 above illustrates one example of aconcrete apparatus structure of FIG. 29. Other various structures may beimplemented to realize one or more of the functions of FIG. 1. Forexample, a DSP may be realized by software.

FIG. 30 is a block diagram illustrating one implementation of a gNB 3060in which systems and methods for ultra-reliable and low-latencycommunication operations may be implemented. The gNB 3060 includestransmit means 3023, receive means 3078 and control means 3082. Thetransmit means 3023, receive means 3078 and control means 3082 may beconfigured to perform one or more of the functions described inconnection with FIG. 1 above. FIG. 28 above illustrates one example of aconcrete apparatus structure of FIG. 30. Other various structures may beimplemented to realize one or more of the functions of FIG. 1. Forexample, a DSP may be realized by software.

FIG. 31 is a flow diagram illustrating a method 3100 of a user equipment(UE) 102. The UE 102 may receive 3102 a radio resource control (RRC)message including a periodicity. The UE 102 may receive 3104 the RRCmessage including a first parameter. The UE 102 may receive 3106 on aphysical downlink control channel, downlink control information (DCI)with cyclic redundancy check (CRC) scrambled by a first radio networktemporary identifier (RNTI) that is different from a cell-RNTI (C-RNTI).The UE 102 may transmit 3108, in a case that the first parameter isconfigured, a first PUSCH transmission based on the periodicity and afirst offset value, the first offset value being configured by using theRRC message. The UE 102 may transmit 3110, in a case that the firstparameter is not configured, a second PUSCH transmission based on theperiodicity and a second offset value, the second offset value beingindicated by using the DCI, the second PUSCH transmission beingactivated by using the DCI.

FIG. 32 is a flow diagram illustrating a communication method 3200 of abase station apparatus (gNB) 160. The gNB 160 may transmit 3202 a radioresource control (RRC) message including a periodicity. The gNB 160 maytransmit 3204 the RRC message including a first parameter. The gNB 160may transmit 3206 on a physical downlink control channel, downlinkcontrol information (DCI) with cyclic redundancy check (CRC) scrambledby a first radio network temporary identifier (RNTI) that is differentfrom a cell-RNTI (C-RNTI). The gNB 160 may receive 3208, in a case thatthe first parameter is configured, a first PUSCH transmission based onthe periodicity and a first offset value, the first offset value beingconfigured by using the RRC message. The gNB 160 may receive 3210, in acase that the first parameter is not configured, a second PUSCHtransmission based on the periodicity and a second offset value, thesecond offset value being indicated by using the DCI, the second PUSCHtransmission being activated by using the DCI.

The term “computer-readable medium” refers to any available medium thatcan be accessed by a computer or a processor. The term“computer-readable medium,” as used herein, may denote a computer-and/or processor-readable medium that is non-transitory and tangible. Byway of example, and not limitation, a computer-readable orprocessor-readable medium may comprise RAM, ROM, EEPROM, CD-ROM or otheroptical disk storage, magnetic disk storage or other magnetic storagedevices, or any other medium that can be used to carry or store desiredprogram code in the form of instructions or data structures and that canbe accessed by a computer or processor. Disk and disc, as used herein,includes compact disc (CD), laser disc, optical disc, digital versatiledisc (DVD), floppy disk and Blu-ray® disc where disks usually reproducedata magnetically, while discs reproduce data optically with lasers.

It should be noted that one or more of the methods described herein maybe implemented in and/or performed using hardware. For example, one ormore of the methods described herein may be implemented in and/orrealized using a chipset, an application-specific integrated circuit(ASIC), a large-scale integrated circuit (LSI) or integrated circuit,etc.

Each of the methods disclosed herein comprises one or more steps oractions for achieving the described method. The method steps and/oractions may be interchanged with one another and/or combined into asingle step without departing from the scope of the claims. In otherwords, unless a specific order of steps or actions is required forproper operation of the method that is being described, the order and/oruse of specific steps and/or actions may be modified without departingfrom the scope of the claims.

It is to be understood that the claims are not limited to the preciseconfiguration and components illustrated above. Various modifications,changes and variations may be made in the arrangement, operation anddetails of the systems, methods, and apparatus described herein withoutdeparting from the scope of the claims.

A program running on the gNB 160 or the UE 102 according to thedescribed systems and methods is a program (a program for causing acomputer to operate) that controls a CPU and the like in such a manneras to realize the function according to the described systems andmethods. Then, the information that is handled in these apparatuses istemporarily stored in a RAM while being processed. Thereafter, theinformation is stored in various ROMs or HDDs, and whenever necessary,is read by the CPU to be modified or written. As a recording medium onwhich the program is stored, among a semiconductor (for example, a ROM,a nonvolatile memory card, and the like), an optical storage medium (forexample, a DVD, a MO, a MD, a CD, a BD, and the like), a magneticstorage medium (for example, a magnetic tape, a flexible disk, and thelike), and the like, any one may be possible. Furthermore, in somecases, the function according to the described systems and methodsdescribed above is realized by running the loaded program, and inaddition, the function according to the described systems and methods isrealized in conjunction with an operating system or other applicationprograms, based on an instruction from the program.

Furthermore, in a case where the programs are available on the market,the program stored on a portable recording medium can be distributed orthe program can be transmitted to a server computer that connectsthrough a network such as the Internet. In this case, a storage devicein the server computer also is included. Furthermore, some or all of thegNB 160 and the UE 102 according to the systems and methods describedabove may be realized as an LSI that is a typical integrated circuit.Each functional block of the gNB 160 and the UE 102 may be individuallybuilt into a chip, and some or all functional blocks may be integratedinto a chip. Furthermore, a technique of the integrated circuit is notlimited to the LSI, and an integrated circuit for the functional blockmay be realized with a dedicated circuit or a general-purpose processor.Furthermore, if with advances in a semiconductor technology, atechnology of an integrated circuit that substitutes for the LSIappears, it is also possible to use an integrated circuit to which thetechnology applies.

Moreover, each functional block or various features of the base stationdevice and the terminal device used in each of the aforementionedimplementations may be implemented or executed by a circuitry, which istypically an integrated circuit or a plurality of integrated circuits.The circuitry designed to execute the functions described in the presentspecification may comprise a general-purpose processor, a digital signalprocessor (DSP), an application specific or general applicationintegrated circuit (ASIC), a field programmable gate array (FPGA), orother programmable logic devices, discrete gates or transistor logic, ora discrete hardware component, or a combination thereof. Thegeneral-purpose processor may be a microprocessor, or alternatively, theprocessor may be a conventional processor, a controller, amicrocontroller or a state machine. The general-purpose processor oreach circuit described above may be configured by a digital circuit ormay be configured by an analogue circuit. Further, when a technology ofmaking into an integrated circuit superseding integrated circuits at thepresent time appears due to advancement of a semiconductor technology,the integrated circuit by this technology is also able to be used.

As used herein, the term “and/or” should be interpreted to mean one ormore items. For example, the phrase “A, B and/or C” should beinterpreted to mean any of: only A, only B, only C, A and B (but not C),B and C (but not A), A and C (but not B), or all of A, B, and C. As usedherein, the phrase “at least one of” should be interpreted to mean oneor more items. For example, the phrase “at least one of A, B and C” orthe phrase “at least one of A, B or C” should be interpreted to mean anyof: only A, only B, only C, A and B (but not C), B and C (but not A), Aand C (but not B), or all of A, B, and C. As used herein, the phrase“one or more of” should be interpreted to mean one or more items. Forexample, the phrase “one or more of A, B and C” or the phrase “one ormore of A, B or C” should be interpreted to mean any of: only A, only B,only C, A and B (but not C), B and C (but not A), A and C (but not B),or all of A, B, and C.

What is claimed is:
 1. A user equipment, comprising: receiving circuitryconfigured to receive a radio resource control (RRC) message comprisinga first parameter used for configuring a periodicity, the receivingcircuitry being configured to receive the RRC message comprising asecond parameter, the receiving circuitry being configured to receive ona physical downlink control channel, downlink control information (DCI)with cyclic redundancy check (CRC) scrambled by a first radio networktemporary identifier (RNTI) that is different from a cell-RNTI (C-RNTI),and transmitting circuitry configured to perform, in a case that thesecond parameter is configured, a first PUSCH transmission based on theperiodicity and a first offset value, the first offset value beingconfigured by using the RRC message, wherein the transmitting circuitryis configured to perform, in a case that the second parameter is notconfigured, a second PUSCH transmission based on the periodicity and asecond offset value, the second offset value being indicated by usingthe DCI, the second PUSCH transmission being activated by using the DCI.2. A base station apparatus comprising: transmitting circuitryconfigured to transmit a radio resource control (RRC) message comprisinga first parameter used for configuring a periodicity, the transmittingcircuitry being configured to transmit the RRC message comprising asecond parameter, the transmitting circuitry being configured totransmit on a physical downlink control channel, downlink controlinformation (DCI) with cyclic redundancy check (CRC) scrambled by afirst radio network temporary identifier (RNTI) that is different from acell-RNTI (C-RNTI), and receiving circuitry configured to receive, in acase that the second parameter is configured, a first PUSCH transmissionbased on the periodicity and a first offset value, the first offsetvalue being configured by using the RRC message, wherein the receivingcircuitry is configured to receive, in a case that the second parameteris not configured, a second PUSCH transmission based on the periodicityand a second offset value, the second offset value being indicated byusing the DCI, the second PUSCH transmission being activated by usingthe DCI.
 3. A communication method of a user equipment comprising:receiving a radio resource control (RRC) message comprising a firstparameter used for configuring a periodicity; receiving the RRC messagecomprising a second parameter; receiving on a physical downlink controlchannel, downlink control information (DCI) with cyclic redundancy check(CRC) scrambled by a first radio network temporary identifier (RNTI)that is different from a cell-RNTI (C-RNTI); transmitting, in a casethat the second parameter is configured, a first PUSCH transmissionbased on the periodicity and a first offset value, the first offsetvalue being configured by using the RRC message; and transmitting, in acase that the second parameter is not configured, a second PUSCHtransmission based on the periodicity and a second offset value, thesecond offset value being indicated by using the DCI, the second PUSCHtransmission being activated by using the DCI.
 4. A communication methodof a base station apparatus comprising: transmitting a radio resourcecontrol (RRC) message comprising a first parameter used for configuringa periodicity; transmitting the RRC message comprising a secondparameter; transmitting on a physical downlink control channel, downlinkcontrol information (DCI) with cyclic redundancy check (CRC) scrambledby a first radio network temporary identifier (RNTI) that is differentfrom a cell-RNTI (C-RNTI); receiving, in a case that the secondparameter is configured, a first PUSCH transmission based on theperiodicity and a first offset value, the first offset value beingconfigured by using the RRC message; and receiving, in a case that thesecond parameter is not configured, a second PUSCH transmission based onthe periodicity and a second offset value, the second offset value beingindicated by using the DCI, the second PUSCH transmission beingactivated by using the DCI.